Re: BUG #6386: PITR never find a consistent recovery point - Mailing list pgsql-bugs

From Euler Taveira de Oliveira
Subject Re: BUG #6386: PITR never find a consistent recovery point
Date
Msg-id 4F099242.9050402@timbira.com
Whole thread Raw
In response to BUG #6386: PITR never find a consistent recovery point  (max.kunz@atip.de)
List pgsql-bugs
On 06-01-2012 15:16, max.kunz@atip.de wrote:
> FATAL:  requested recovery stop point is before consistent recovery point.
>
> One system is configured as standby, performing stream and WAL replication.
> Another system is running in primary mode.
> I have verified that the standby system performed the basebackup
> successfully. Hours later I did like to perform a PITR. I use a target_time
> which is one hour later than stop_basebackup_time. In spite of that fact,
> i've got the error message.
>
It doesn't seem a bug. Are you sure the time choosen is *after* you send a
pg_stop_backup()?


--
   Euler Taveira de Oliveira - Timbira       http://www.timbira.com.br/
   PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento

pgsql-bugs by date:

Previous
From: max.kunz@atip.de
Date:
Subject: BUG #6386: PITR never find a consistent recovery point
Next
From: Tom Lane
Date:
Subject: Re: BUG #6385: extract epoch at timezone returns wrong value