From: | Ron <ronljohnsonjr(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Validate the internal consistency of pg_dump output? |
Date: | 2022-09-22 15:16:43 |
Message-ID: | f9d0f7ef-baeb-08f0-066b-f62af7d34c66@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
In my case, it's directory format backups.
(I'm not asking whether the pg_dump output is exactly the same as the data
in the database; that can only be done inside of pg_dump, and I don't see
any option for that anyway.)
Is there a tool for validating that:
- there are "\N" lines at the end of every NNNN.dat(.gz) file,
- toc.dat isn't "missing" data at the end of the file, and that
- there are NNNN.dat(.gz) files corresponding to all the tables mentioned in
toc.dat?
The use case would be in validating that pg_dump actually dumped all the
data when there's a question of whether or not it completed.
--
Angular momentum makes the world go 'round.
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2022-09-22 15:23:20 | Re: [PATCH] Introduce array_shuffle() and array_sample() |
Previous Message | Ron | 2022-09-22 14:56:45 | Re: pg_dump failed with error code 255, but I don't see why |