Re: pg_dump end comment - Mailing list pgsql-hackers

From Philip Warner
Subject Re: pg_dump end comment
Date
Msg-id 6.0.0.22.0.20040331112420.046b4598@203.8.195.10
Whole thread Raw
In response to Re: pg_dump end comment  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: pg_dump end comment  ("scott.marlowe" <scott.marlowe@ihs.com>)
List pgsql-hackers
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.



----------------------------------------------------------------
Philip Warner                    |     __---_____
Albatross Consulting Pty. Ltd.   |----/       -  \
(A.B.N. 75 008 659 498)          |          /(@)   ______---_
Tel: (+61) 0500 83 82 81         |                 _________  \
Fax: (+61) 03 5330 3172          |                 ___________ |
Http://www.rhyme.com.au          |                /           \|                                 |    --________--
PGP key available upon request,  |  /
and from pgp.mit.edu:11371       |/ 



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: psql \d option list overloaded
Next
From: Christopher Kings-Lynne
Date:
Subject: Re: pg_dump end comment