Use PgBackRest or pg_basebackup. Not only do they correctly handle wal files, but do checksums.
On Mon, Oct 21, 2024 at 11:51 AM Murthy Nunna <mnunna@fnal.gov> wrote:
Hi Muhammad,
Thank you for responding to my query.
I don’t think checksum method will work in my situation because the source file would have changed by the time I run checksum. So, the checksum (or diff) will be different.
I am doing rsync of active cluster.
What I am looking for is physical (structural) verification of target file such as beginning block and end block, beginning of file and end of file etc. All I want to know is “completeness” and “readability” of the file by postgres.
or do checksum on source and target and take diff between two checksum generated files e.g.
cd /pgdata find . -type f -exec sha256sum {} \; > /tmp/source_checksums.txt
Regards,
Ikram
On Sun, Oct 20, 2024 at 4:45 AM Murthy Nunna <mnunna@fnal.gov> wrote:
Hi,
We are currently using pg_waldump to verify integrity of WAL files after archiving them in external storage. If the WAL is incomplete pg_waldump returns error, which is great.
Similarly, I am wondering if there is any utility that can be used against data files in /pgdata. Just to verify after “rsync” of /pgdata.