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" ??
Please help !
Thanks
VB
On Mon, Sep 26, 2011 at 5:11 PM, Venkat Balaji
<venkat.balaji@verse.in> wrote:
Hello Everyone,
We have had situations where-in "rsync" was executed without executing "pg_start_backup()" on the production data directory and on the next runs, "pg_start_backup()" has been executed with "rsync". This was to avoid high IO load on production. We ended up getting unmatched files (especially in pg_clog) and not sure about "base" directory.
Postgres is asking for WAL Archive files dated sometime around 15 days ago. We are absolutely not sure whats going on.
Is this dangerous for production (like corruption) ? or just the backup will be invalid ? Please help us know if we have to perform any precautionary checks on the production cluster.
Apart from firing a checkpoint, does "pg_start_backup()" updates any dictionary tables or views ? or it updates anything in "pg_xlog"
Looking forward for your help !
Thanks
VB
