[prev in list] [next in list] [prev in thread] [next in thread] 

List:       postgresql-general
Subject:    Re: [HACKERS] pg_dump end comment
From:       "scott.marlowe" <scott.marlowe () ihs ! com>
Date:       2004-03-31 15:53:10
Message-ID: Pine.LNX.4.33.0403310852360.26243-100000 () css120 ! ihs ! com
[Download RAW message or body]

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.


---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org
[prev in list] [next in list] [prev in thread] [next in thread]