Our problem is -
We had mistakenly executed "rsync" on the running PostgreSQL data directory (production) and we did not run "pg_start_backup()".
Will this harm production ? can this lead to corruption ?
Thanks -
On Mon, Sep 26, 2011 at 10:29 PM, Alan Hodgson <ahodgson@xxxxxxxxx> wrote:
On September 26, 2011 05:49:50 AM Venkat Balaji wrote:The archive files are created by your archive_command, as specified in
> I tried restoring the backup, after taking the full backup.
>
> Below is what i see in the "archive destination".
>
> Postgres was asking for "00000001000001930000006F" and i tried to find the
> same and below is what i find...
>
> -rw------- 1 postgres postgres 3.3M Sep 26 02:06
> 00000001000001930000006F.gz -rw------- 1 postgres postgres 219 Sep 26
> 02:53
> 00000001000001930000006F.00328508.backup.gz
>
> Why is PG (9.0) putting an extension for the WAL Archive file as
> > "backup.gz" ??
>
postgresql.conf. My guess would be that your archive command runs the files
through gzip as part of archiving (which is fine).
However, the restore_command you specify in recovery.conf must undo this
compression. So instead of (for example) 'cp -f "%f" "%p"', it might instead
need to look like 'zcat "%f" > "%p"'.
Hope this helps.
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
