From: | Euler Taveira de Oliveira <euler(at)timbira(dot)com> |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Cc: | max(dot)kunz(at)atip(dot)de |
Subject: | Re: BUG #6386: PITR never find a consistent recovery point |
Date: | 2012-01-08 12:55:30 |
Message-ID: | 4F099242.9050402@timbira.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On 06-01-2012 15:16, max(dot)kunz(at)atip(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2012-01-08 16:19:18 | Re: BUG #6385: extract epoch at timezone returns wrong value |
Previous Message | Tom Lane | 2012-01-07 17:42:48 | Re: [PATCH v3] Use CC atomic builtins on ARM |