Re: BUG: Former primary node might stuck when started as a standby - Mailing list pgsql-hackers

From Alexander Lakhin
Subject Re: BUG: Former primary node might stuck when started as a standby
Date
Msg-id 4becfd72-014c-40a7-b2fc-d41e92b1856b@gmail.com
Whole thread Raw
In response to Re: BUG: Former primary node might stuck when started as a standby  (Michael Paquier <michael@paquier.xyz>)
Responses Re: BUG: Former primary node might stuck when started as a standby
List pgsql-hackers
04.03.2026 10:23, Michael Paquier wrote:
> Did you find any buildfarm failures involving 028?  I cannot get
> excited in changing tests where nothing has happened, and this test
> looks OK as we don't do a switchover.  For 004, we have at least one
> failure recorded based on what you said.  That's a fact sufficient for
> me to fix things, for 004.

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.

Best regards,
Alexander



pgsql-hackers by date:

Previous
From: Chao Li
Date:
Subject: Re: eliminate xl_heap_visible to reduce WAL (and eventually set VM on-access)
Next
From: "Jelte Fennema-Nio"
Date:
Subject: Re: Add "format" target to make and ninja to run pgindent and pgperltidy