| From: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com> |
|---|---|
| To: | Philip Warner <pjw(at)rhyme(dot)com(dot)au> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Gavin Sherry <swm(at)linuxworld(dot)com(dot)au>, 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 15:53:10 |
| Message-ID: | Pine.LNX.4.33.0403310852360.26243-100000@css120.ihs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2004-03-31 15:55:04 | Re: logging statement levels |
| Previous Message | Andrew Dunstan | 2004-03-31 15:23:28 | Re: logging statement levels |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2004-03-31 15:55:04 | Re: logging statement levels |
| Previous Message | Andrew Dunstan | 2004-03-31 15:23:28 | Re: logging statement levels |