Skip site navigation (1) Skip section navigation (2)

Re: pg_dump end comment

From: Philip Warner <pjw(at)rhyme(dot)com(dot)au>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>,Gavin Sherry <swm(at)linuxworld(dot)com(dot)au>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>,Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>,Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_dump end comment
Date: 2004-03-31 01:26:31
Message-ID: 6.0.0.22.0.20040331112420.046b4598@203.8.195.10 (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
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       |/ 


In response to

Responses

pgsql-hackers by date

Next:From: Christopher Kings-LynneDate: 2004-03-31 01:36:36
Subject: Re: pg_dump end comment
Previous:From: Bruce MomjianDate: 2004-03-31 01:06:25
Subject: Re: psql \d option list overloaded

pgsql-patches by date

Next:From: Christopher Kings-LynneDate: 2004-03-31 01:36:36
Subject: Re: pg_dump end comment
Previous:From: Alvaro HerreraDate: 2004-03-30 23:37:28
Subject: xact.c cleanup -- uncontroversial try

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group