| From: | Christophe Pettus <xof(at)thebuild(dot)com> |
|---|---|
| To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | requested timeline ... does not contain minimum recovery point ... |
| Date: | 2018-07-12 17:20:06 |
| Message-ID: | 5A7F0B60-28BC-4EF0-B2EF-9D6AA47A0378@thebuild.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
--
-- Christophe Pettus
xof(at)thebuild(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2018-07-12 17:29:25 | Re: requested timeline ... does not contain minimum recovery point ... |
| Previous Message | Alvaro Herrera | 2018-07-12 17:15:41 | Re: Cannot dump foreign key constraints on partitioned table |