From: | Igor Neyman <ineyman(at)perceptron(dot)com> |
---|---|
To: | Gary <listgj-pg(at)yahoo(dot)co(dot)uk>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: How to verify pg_dump files |
Date: | 2012-11-07 19:56:30 |
Message-ID: | A76B25F2823E954C9E45E32FA49D70EC08EEDB6C@mail.corp.perceptron.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> -----Original Message-----
> From: Gary [mailto:listgj-pg(at)yahoo(dot)co(dot)uk]
> Sent: Wednesday, November 07, 2012 8:02 AM
> To: pgsql-general(at)postgresql(dot)org
> Subject: How to verify pg_dump files
>
> 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?
>
> --
> Gary Please do NOT send me 'courtesy' replies off-list.
>
The only 100% fool-proof test would be to restore from your backup files.
Regards,
Igor Neyman
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2012-11-07 19:58:06 | Re: [GENERAL] Error registering at postgresql.org |
Previous Message | Lists | 2012-11-07 19:54:48 | Re: Unexpectedly high disk space usage |