Validate the internal consistency of pg_dump output? - Mailing list pgsql-general

From Ron
Subject Validate the internal consistency of pg_dump output?
Date
Msg-id f9d0f7ef-baeb-08f0-066b-f62af7d34c66@gmail.com
Whole thread Raw
List 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.



pgsql-general by date:

Previous
From: Ron
Date:
Subject: Re: pg_dump failed with error code 255, but I don't see why
Next
From: Laurenz Albe
Date:
Subject: Re: Database Horizon