Add system identifier to backup manifest
Amul Sul <sulamul@gmail.com>
From: Amul Sul <sulamul@gmail.com>
To: PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2024-01-17T11:30:52Z
Lists: pgsql-hackers
Attachments
- v1-0001-Add-system-identifier-to-backup-manifest.patch (application/x-patch) patch v1-0001
Hi All, With the attached patch, the backup manifest will have a new key item as "System-Identifier" 64-bit integer whose value is derived from pg_control while generating it, and the manifest version bumps to 2. This helps to identify the correct database server and/or backup for the subsequent backup operations. pg_verifybackup validates the manifest system identifier against the backup control file and fails if they don’t match. Similarly, pg_basebackup increment backup will fail if the manifest system identifier does not match with the server system identifier. The pg_combinebackup is already a bit smarter -- checks the system identifier from the pg_control of all the backups, with this patch the manifest system identifier also validated. For backward compatibility, the manifest system identifier validation will be skipped for version 1. -- Regards, Amul Sul EDB: http://www.enterprisedb.com
Commits
-
Add the system identifier to backup manifests.
- 2041bc4276c9 17.0 landed
-
pg_verifybackup: Refactor parse_manifest_file.
- dc8f2d7c064a 17.0 landed
-
Add option force_initdb to PostgreSQL::Test::Cluster:init()
- ff9e1e764fcc 17.0 landed