| From: | Ryan Delaney <ryan(dot)delaney(at)gmail(dot)com> |
|---|---|
| To: | rod(at)iol(dot)ie |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: How to verify pg_dump files |
| Date: | 2012-11-07 18:57:48 |
| Message-ID: | CAN0-qtg4FeyQTTma9YFB=ir30ghMUpT-nvfOSvZp2uGEgq4Zcg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Nov 7, 2012 at 10:11 AM, Raymond O'Donnell <rod(at)iol(dot)ie> wrote:
> On 07/11/2012 13:01, Gary wrote:
> > Can anyone suggest how I could verify that the files created by pg_dump
> > are "okay"? They are being created for backup purposes, and the last
> > thing I want to do is find out that the backups themselves are in some
> > way corrupt.
> >
> > I know I can check the output of the command itself, but what if.. I
> > don't know... if there are problems with the disc it writes to, or
> > something like that. Is there any way to check whether the output file
> > is "valid" in the sense that it is complete and syntactically correct?
>
> Reload it and test your application against it?
>
> Ray.
>
>
> --
> Raymond O'Donnell :: Galway :: Ireland
> rod(at)iol(dot)ie
>
>
Would that entail over-writing good data with possibly bad data?
Ryan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nicholas Wilson | 2012-11-07 18:58:02 | Unique/Primary key not inherited in partition, workaround? |
| Previous Message | Raymond O'Donnell | 2012-11-07 18:11:51 | Re: How to verify pg_dump files |