pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #17640: fork off the requested timeline before the switchpoint.
2+ messages / 2 participants
[nested] [flat]
* BUG #17640: fork off the requested timeline before the switchpoint.
@ 2022-10-14 05:21 PG Bug reporting form <noreply@postgresql.org>
0 siblings, 1 reply; 2+ messages in thread
From: PG Bug reporting form @ 2022-10-14 05:21 UTC (permalink / raw)
To: pgsql-bugs@lists.postgresql.org; +Cc: mukeshsingh.singh19@gmail.com
The following bug has been logged on the website:
Bug reference: 17640
Logged by: Mukesh Singh
Email address: mukeshsingh.singh19@gmail.com
PostgreSQL version: 11.5
Operating system: linux
Description:
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.
2022-10-14 06:21:03 WAT 2022-10-14 06:21:03.977 WAT [63168] LOG: startup
process (PID 63170) exited with exit code 1
2022-10-14 06:21:03 WAT 2022-10-14 06:21:03.977 WAT [63168] LOG: aborting
startup due to startup process failure
2022-10-14 06:21:03 WAT 2022-10-14 06:21:03.978 WAT [63168] LOG: database
system is shut down
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: BUG #17640: fork off the requested timeline before the switchpoint.
@ 2022-10-15 02:47 Michael Paquier <michael@paquier.xyz>
parent: PG Bug reporting form <noreply@postgresql.org>
0 siblings, 0 replies; 2+ messages in thread
From: Michael Paquier @ 2022-10-15 02:47 UTC (permalink / raw)
To: mukeshsingh.singh19@gmail.com; pgsql-bugs@lists.postgresql.org
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
Attachments:
signature.asc (application/pgp-signature, 832B) download
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2022-10-15 02:47 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2022-10-14 05:21 BUG #17640: fork off the requested timeline before the switchpoint. PG Bug reporting form <noreply@postgresql.org>
2022-10-15 02:47 ` Michael Paquier <michael@paquier.xyz>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox