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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Imre Oolberg <imre(at)auul(dot)pri(dot)ee>
Cc: Scott Ribe <scott_ribe(at)elevated-dev(dot)com>, pgsql-admin(at)postgresql(dot)org
Subject: Re: Re: pg v. 8.4.5 misses objects and data after restoring from backup using wal
Date: 2011-01-03 20:24:26
Message-ID: 24373.1294086266@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Imre Oolberg <imre(at)auul(dot)pri(dot)ee> writes:
> First of all, thanks for your time dealing with my situation. I must
> stress that i have wal arhived starting from before issuing
> pg_start_backup, wal archives generated before pg_start/stop_backup and
> also some wal archive files generated after pg_stop_backup (and
> permissions are ok). But for some reason my replay starts exactly where
> .backup file says 'stop wal location', referring to my earlier post

> STOP WAL LOCATION: 1/6325B2E0 (file 000000010000000100000063)

> I am starting to think more in the direction what Kevin Grittner
> suggested that i miss something in my procedure and instead following so
> to say recovery path i am doing something else which strangely ends up
> with working database process but actually misses some data.

I wonder whether you're failing to copy the backup_label file as part of
the base backup. The presence of that file is what tells the slave
postmaster where it has to start recovering from.

regards, tom lane

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Kevin Grittner 2011-01-03 20:37:56 Re: Re: pg v. 8.4.5 misses objects and data after restoring from backup using wal
Previous Message Imre Oolberg 2011-01-03 20:15:01 Re: Re: pg v. 8.4.5 misses objects and data after restoring from backup using wal