Thanks, Laurenz Albe.
I found an article that explains a similar situation to the one I faced.
https://www.alibabacloud.com/blog/how-to-avoid-timeline-errors-during-database-switchover-based-on-asynchronous-streaming-replication_597819
-----Original Message-----
From: Laurenz Albe <laurenz.albe@cybertec.at>
Sent: Friday, January 31, 2025 3:37 PM
To: di.liu@japannext.co.jp; pgsql-admin@lists.postgresql.org
Subject: Re: PostgreSQL Timeline Issue After Switchover with Pacemaker
On Fri, 2025-01-31 at 09:09 +0900, di.liu@japannext.co.jp wrote:
> Why, after a full backup restore, did the standby still look for the wrong timeline?
> Is there a file or setting that records the timeline information?
It is hard to say what exactly happened, since I don't know your exact setup, but very likely a standby server got
promoted,started a new timeline 8 and archived the corresponding history file. But somehow the rest of the cluster
didn'tfollow that promotion. Now upon every restore attempt, the history file gets fetched from the WAL archive and
causesconfusion.
Yours,
Laurenz Albe
--
_This correspondence (including any attachments) is for the intended
recipient(s) only. It may contain confidential or privileged information or
both. No confidentiality or privilege is waived or lost by any
mis-transmission. If you receive this correspondence by mistake, please
contact the sender immediately, delete this correspondence (and all
attachments) and destroy any hard copies. You must not use, disclose, copy,
distribute or rely on any part of this correspondence (including any
attachments) if you are not the intended
recipient(s).本メッセージに記載および添付されている情報（以下、総称して「本情報」といいます。）は、本来の受信者による使用のみを意図しています。誤送信等により本情報を取得された場合でも、本情報に係る秘密、または法律上の秘匿特権が失われるものではありません。本電子メールを受取られた方が、本来の受信者ではない場合には、本情報及びそのコピーすべてを削除・破棄し、本電子メールが誤って届いた旨を発信者宛てにご通知下さいますようお願いします。本情報の閲覧、発信または本情報に基づくいかなる行為も明確に禁止されていることをご了承ください。_
