Re: BUG #17640: fork off the requested timeline before the switchpoint. - Mailing list pgsql-bugs

From Michael Paquier
Subject Re: BUG #17640: fork off the requested timeline before the switchpoint.
Date
Msg-id Y0ofVYQCpeODGUKA@paquier.xyz
Whole thread Raw
In response to BUG #17640: fork off the requested timeline before the switchpoint.  (PG Bug reporting form <noreply@postgresql.org>)
List pgsql-bugs
On Fri, Oct 14, 2022 at 05:21:48AM +0000, PG Bug reporting form wrote:
> 2022-10-14 06:21:03 WAT 2022-10-14 06:21:03.969 WAT [63170] LOG:  restored
> log file "0000003400004E7500000029" from archive
> 2022-10-14 06:21:03 WAT 2022-10-14 06:21:03.976 WAT [63170] FATAL:
> requested timeline 53 is not a child of this server's history
> 2022-10-14 06:21:03 WAT 2022-10-14 06:21:03.976 WAT [63170] DETAIL:  Latest
> checkpoint is at 4E75/2930CB38 on timeline 52, but in the history of the
> requested timeline, the server forked off from that timeline at
> 4B77/F5FFF080.

Well, this points out that the timeline you have selected is not the
one your timeline history file likes.  I fail to see why this would be
a bug without more details about your configuration (including
archiving strategy) and what you did with your set of servers when
doing a failover, for example.
--
Michael

Attachment

pgsql-bugs by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: BUG #17637: case-when branches taken even if they dont match, raising errors
Next
From: PG Bug reporting form
Date:
Subject: BUG #17641: postgresql service persistently restarts because "could not open shared memory segment"