On Thu, Nov 13, 2014 at 2:45 AM, Josh Berkus <josh@agliodbs.com> wrote:
> On 11/12/2014 10:06 AM, Robert Haas wrote:
>>> hat *appears* to be happening is that the pause_at_recovery_target,
>>> > followed by the restart, on the replica causes it to advance one commit
>>> > on timeline 1. But *not all the time*; this doesn't happen in my
>>> > pgbench-based tests.
>>> >
>>> > There's a workaround for the user (they just restore the replica to 5
>>> > minutes earlier), but I'm thinking this is a minor bug somewhere.
>> I'm not sure what's going on here, but keep in mind that when you
>> restart the replica, it's going to back up to the most recent
>> restartpoint and begin replication from there, not from the point it
>> was at when you shut down.
>
> Except that in the problem case, it appears to be going *forwards*.
> What would cause that?
Unfortunately, I have no idea.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
