| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Greg Stark <stark(at)mit(dot)edu>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: recovery_target_time and standby_mode |
| Date: | 2014-11-13 07:45:54 |
| Message-ID: | 546461B2.6070800@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2014-11-13 08:05:59 | Re: Failback to old master |
| Previous Message | Amit Kapila | 2014-11-13 07:34:56 | Re: TODO : Allow parallel cores to be used by vacuumdb [ WIP ] |