| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Christophe Pettus <xof(at)thebuild(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: requested timeline ... does not contain minimum recovery point ... |
| Date: | 2018-07-12 17:29:25 |
| Message-ID: | 20180712172925.aqb3lhtilia6is5j@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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 WAL-shipping (not streaming) secondary starts up.
>
> These two machines have been part of a stress-test where, repeatedly, the secondary is promoted, the old primary is rewound using pg_rewind, and then attached to the new primary. This has worked for multiple iterations, but this error popped up. The last cycle was particularly fast: the new primary was only up for about 10 seconds (although it had completed recovery) before being shut down again, and pg_rewind applied to it to reconnect it with the promoted secondary.
This needs a lot more information before somebody can reasonably act on
it.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fabien COELHO | 2018-07-12 18:27:14 | Re: [HACKERS] Re: [COMMITTERS] pgsql: Remove pgbench "progress" test pending solution of its timing is (fwd) |
| Previous Message | Christophe Pettus | 2018-07-12 17:20:06 | requested timeline ... does not contain minimum recovery point ... |