> On Jul 12, 2018, at 19:54, Andres Freund wrote:
> Do you see a "checkpoint complete: wrote ..." message
> before the rewind started?
Checking, but I suspect that's exactly the problem.
This raises a question: Would it make sense for pg_rewind to either force a
checkpoint or have a --checkpo
On 2018-07-12 19:22:50 -0700, Christophe Pettus wrote:
>
> > On Jul 12, 2018, at 17:52, Michael Paquier wrote:
> > Wild guess: you did not issue a checkpoint on the promoted standby
> > before running pg_rewind.
>
> I don't believe a manual checkpoint was done on the target (promoted standby,
>
> On Jul 12, 2018, at 19:22, Christophe Pettus wrote:
>
>
>> On Jul 12, 2018, at 17:52, Michael Paquier wrote:
>> Wild guess: you did not issue a checkpoint on the promoted standby
>> before running pg_rewind.
>
> I don't believe a manual checkpoint was done on the target (promoted standby,
> On Jul 12, 2018, at 17:52, Michael Paquier wrote:
> Wild guess: you did not issue a checkpoint on the promoted standby
> before running pg_rewind.
I don't believe a manual checkpoint was done on the target (promoted standby,
new master), but it did one as usual during startup after the timel
On Thu, Jul 12, 2018 at 02:26:17PM -0700, Christophe Pettus wrote:
> What surprises me about the error is that while the recovery point
> seems reasonable, it shouldn't be on timeline 103, but on timeline
> 105.
Wild guess: you did not issue a checkpoint on the promoted standby
before running pg_r
> On Jul 12, 2018, at 10:29, Andres Freund wrote:
>
> This needs a lot more information before somebody can reasonably act on
> it.
Happy to provide, of course!
The two relevant hosts are "Ash" and "Chi". As mentioned, they've been flipped
back and forth repeatedly using pg_rewind: One will
Hi,
On 2018-07-12 10:20:06 -0700, Christophe Pettus wrote:
> PostgreSQL 9.6.9, Windows Server 2012 Datacenter (64-bit).
>
> We're trying to diagnose the error:
>
> requested timeline 105 does not contain minimum recovery point
> A58/6B109F28 on timeline 103
>
> The error occurs when a WA
PostgreSQL 9.6.9, Windows Server 2012 Datacenter (64-bit).
We're trying to diagnose the error:
requested timeline 105 does not contain minimum recovery point
A58/6B109F28 on timeline 103
The error occurs when a WAL-shipping (not streaming) secondary starts up.
These two machines have b
