Re: BUG: Former primary node might stuck when started as a standby

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Alexander Lakhin <exclusion(at)gmail(dot)com>
Cc: "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Aleksander Alekseev <aleksander(at)timescale(dot)com>
Subject: Re: BUG: Former primary node might stuck when started as a standby
Date: 2026-03-05 01:08:18
Message-ID: aajXgmZjROQvPGpY@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Mar 04, 2026 at 11:00:00AM +0200, Alexander Lakhin wrote:
> No, I didn't. I agree that eliminating already known failures makes more
> sense. Anyway, we'll have the thread which explain why such failures can
> happen.

Fixed this second instability now with the same trick as 009, down to
v14, as there is no strong requirement for an immediate stop of the
primary to check that a standby is able to to a TLI jump when
reconnecting to the promoted standby.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Chao Li 2026-03-05 01:13:06 Re: astreamer_lz4: fix bug of output pointer advancement in decompressor
Previous Message Tomas Vondra 2026-03-05 01:01:32 Re: [PATCH] Fix improper tuple deallocation in import_pg_statist()