Re: pg v. 8.4.5 misses objects and data after restoring from backup using wal

[Imre Oolberg <imre@xxxxxxxxxxx>]

On 01/03/11 19:36, Kevin Grittner wrote:

Imre Oolberg <imre@xxxxxxxxxxx> 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?
 
  

Yep, that works as it is since wal files are created althought to use %f should not hurt either.

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?
  

I have there exactly one line

restore_command = 'cp /data/backup/postgresql/archive-logs/%f %p'

and with it i expect to restore as much data as i have wal files archived. The most strange thing is that it uses archived wal files which are generated after pg_stop_backup but skips all others.


Imre

 
-Kevin