Re: pg v. 8.4.5 misses objects and data after restoring from backup using wal - Mailing list pgsql-admin

From Kevin Grittner
Subject Re: pg v. 8.4.5 misses objects and data after restoring from backup using wal
Date
Msg-id 4D21B4AE0200002500038F48@gw.wicourts.gov
Whole thread Raw
In response to Re: pg v. 8.4.5 misses objects and data after restoring from backup using wal  (Imre Oolberg <imre@auul.pri.ee>)
Responses Re: pg v. 8.4.5 misses objects and data after restoring from backup using wal
List pgsql-admin
Imre Oolberg <imre@auul.pri.ee> wrote:

> archive_command = 'test ! -f
> /data/backup/postgresql/archive-logs/%f &&
> cp %p /data/backup/postgresql/archive-logs'

I suppose that will work, but why not specify %f in the copy target?

> I guess that my problem is probably that although my .backup file
> says
>
> 000000010000000000000009.00000020.backup
> START WAL LOCATION: 0/9000020 (file 000000010000000000000009)
> STOP WAL LOCATION: 1/6325B2E0 (file 000000010000000100000063)
> CHECKPOINT LOCATION: 0/A2C4908
> START TIME: 2011-01-03 11:32:17 EET
> LABEL: test
> STOP TIME: 2011-01-03 12:18:27 EET
>
> looking at the pg_ctl.log it starts reading wal logs beginning
> with 000000010000000100000063 and not with
> 000000010000000000000009

What did you have in your recovery.conf file?

-Kevin

pgsql-admin by date:

Previous
From: bricklen
Date:
Subject: Re: Greenplum: Functions that execute SQL statements from the segDBs are not yet supported.
Next
From: Imre Oolberg
Date:
Subject: Re: Re: pg v. 8.4.5 misses objects and data after restoring from backup using wal