On 2/27/20 9:22 PM, Robert Haas wrote:
Here's a new patch set for this feature.
Thanks Robert. After applying all the 5 patches (v8-00*) against PG v13
(commit id -afb5465e0cfce7637066eaaaeecab30b0f23fbe3) ,
There are few issues/observations
1)Getting segmentation fault error if we try pg_validatebackup against
a valid backup_manifest file but data directory path is WRONG
[centos@tushar-ldap-docker bin]$ ./pg_basebackup -D bk
--manifest-checksums=sha224
[centos@tushar-ldap-docker bin]$ cp bk/backup_manifest /tmp/.
[centos@tushar-ldap-docker bin]$ ./pg_validatebackup -m
/tmp/backup_manifest random_directory/
pg_validatebackup: * manifest_checksum =
f0460cd6aa13cf0c5e35426a41af940a9231e6425cd65115a19778b7abfdaef9
pg_validatebackup: error: could not open directory "random_directory":
No such file or directory
Segmentation fault
2) when used '-R' option at the time of create base backup
[centos@tushar-ldap-docker bin]$ ./pg_basebackup -D bar -R
[centos@tushar-ldap-docker bin]$ ./pg_validatebackup bar
pg_validatebackup: * manifest_checksum =
a195d3a3a82a41200c9ac92c12d764d23c810e7e91b31c44a7d04f67ce012edc
pg_validatebackup: error: "standby.signal" is present on disk but not in
the manifest
pg_validatebackup: error: "postgresql.auto.conf" has size 286 on disk
but size 88 in the manifest
[centos@tushar-ldap-docker bin]$
--
regards,tushar
EnterpriseDB https://www.enterprisedb.com/
The Enterprise PostgreSQL Company
