1

I am very new to PostgreSQL. I have built an evaluation/testing environment. Following series of steps describe my issue.

Environment details:

Non-Production  
Postgresql version : 16.9
OS : AlmaLinux 8.10 (Cerulean Leopard)
Postgresql data directory : /var/lib/16/data
User defined tablespaces location : /var/lib/16/data2 

I ran pg_basebackup using the following command :

    pg_basebackup -D /apps/stage/backups/20250912 \
--tablespace-mapping=/var/lib/pgsql/16/data2/cookbook_data=/apps/stage/backups/20250912/cookbook_data \
--tablespace-mapping=/var/lib/pgsql/16/data2/cookbook_indexes=/apps/stage/backups/20250912/cookbook_indexes --tablespace-mapping=/var/lib/pgsql/16/data2/cookbook_data2=/apps/stage/backups/20250912/cookbook_data2

The backup ran successfully. Did not see any error messages on the screen. Output of above command:

pg_basebackup: initiating base backup, waiting for checkpoint to complete
pg_basebackup: checkpoint completed
pg_basebackup: write-ahead log start point: 0/7E000028 on timeline 1
pg_basebackup: starting background WAL receiver
pg_basebackup: created temporary replication slot "pg_basebackup_836137"
pg_basebackup: write-ahead log end point: 0/7E000100
pg_basebackup: waiting for background process to finish streaming ...
pg_basebackup: syncing data to disk ...
pg_basebackup: renaming backup_manifest.tmp to backup_manifest
pg_basebackup: base backup completed

I tried to run pg_verifybackup utility against the backup directory:

pg_verifybackup /apps/stage/backups/20250912

It displays a series of these error messages:

pg_verifybackup: error: "cookbook_data/PG_16_202307071/16462/PG_VERSION" is present on disk but not in the manifest
pg_verifybackup: error: "cookbook_data/PG_16_202307071/16462/3542" is present on disk but not in the manifest
pg_verifybackup: error: "cookbook_data/PG_16_202307071/16462/2228" is present on disk but not in the manifest
pg_verifybackup: error: "cookbook_data/PG_16_202307071/16462/pg_filenode.map" is present on disk but not in the manifest
pg_verifybackup: error: "cookbook_data/PG_16_202307071/16462/2619" is present on disk but not in the manifest

Is this an issue? Can we ignore these errors safely? Is there any specific parameter that I need to set while running pg_basebackup or pg_verifybackup utilities? Is there a way to get rid of these error messages?

I went thru all the parameters for these utilities. Could not find a clue.

ls -l /apps/stage/backups/20250912/pg_tblspc
total 0
lrwxrwxrwx. 1 postgres postgres 42 Sep 12 13:05 16460 -> /apps/stage/backups/20250912/cookbook_data
lrwxrwxrwx. 1 postgres postgres 45 Sep 12 13:05 16461 -> /apps/stage/backups/20250912/cookbook_indexes
lrwxrwxrwx. 1 postgres postgres 43 Sep 12 13:05 16469 -> /apps/stage/backups/20250912/cookbook_data2

Kindly guide me how to get rid of these errors.

Thanks and Regards.

4
  • Thanks for looking into this. I am unable to print each line of output as separate line. Putting one comment for each line: ls -l /apps/stage/backups/20250912/pg_tblspc Commented Sep 15 at 8:46
  • lrwxrwxrwx. 1 postgres postgres 42 Sep 12 13:05 16460 -> /apps/stage/backups/20250912/cookbook_data Commented Sep 15 at 8:46
  • lrwxrwxrwx. 1 postgres postgres 45 Sep 12 13:05 16461 -> /apps/stage/backups/20250912/cookbook_indexes Commented Sep 15 at 8:46
  • lrwxrwxrwx. 1 postgres postgres 43 Sep 12 13:05 16469 -> /apps/stage/backups/20250912/cookbook_data2 Commented Sep 15 at 8:46

1 Answer 1

0

At least the files PG_VERSION and pg_filenode.map should not exist in your tablespace, and the error message suggests that they didn't when the backup was taken. Somebody must have copied extra files into the backup, and pg_verifybackup's complaints are justified. How else would these files end up there? Perhaps check the timestamp on these files.

1
  • Will verify those files. Thank you. Commented Sep 15 at 9:18

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.