Re: pg_dump end comment - Mailing list pgsql-hackers

From scott.marlowe
Subject Re: pg_dump end comment
Date
Msg-id Pine.LNX.4.33.0403310852360.26243-100000@css120.ihs.com
Whole thread Raw
In response to Re: pg_dump end comment  (Philip Warner <pjw@rhyme.com.au>)
List pgsql-hackers
On Wed, 31 Mar 2004, Philip Warner wrote:

> At 12:13 AM 31/03/2004, Bruce Momjian wrote:
> >Yes, they have to check for a proper exit from pg_dump, but there is
> >still a file sitting around after the dump, with no way to tell if it is
> >accurate.
> 
> Why don't we write a hash into the header or footer. Then use something like:
> 
>      pg_restore --verify <dump-file>
> 
> if file integrity is the objective.

I like this idea.  Nice to be able to check the md5 sig to make sure a 
backup is not corrupted OR short.



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Why is pg_dump using INSERTs instead of COPYs?
Next
From: Tom Lane
Date:
Subject: Re: with vs without oids in pg_catalog.*