Request a Demo
Home   >   mailing lists

Re: Fix "unexpected logical decoding status change" error; from concurrent logical decoding activation - Mailing list pgsql-hackers

From Masahiko Sawada
Subject Re: Fix "unexpected logical decoding status change" error; from concurrent logical decoding activation
Date
Msg-id CAD21AoBifn_w=AuH1Cda4ijrxzFkkckKN1v1v=BddL_5qgQ89g@mail.gmail.com
Whole thread
In response to Re: Fix "unexpected logical decoding status change" error; from concurrent logical decoding activation  (Masahiko Sawada <sawada.mshk@gmail.com>)
Responses Re: injection_points: Switch wait/wakeup to use atomics rather than latches
List pgsql-hackers
Tree view 
On Thu, Jul 30, 2026 at 9:01 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> Masahiko Sawada <sawada.mshk@gmail.com> writes:
> > On Thu, Jul 30, 2026 at 5:52 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> >> The buildfarm looks like this has made 051_effective_wal_level.pl
> >> less stable, not more so.  The failures all look like
>
> > What does the buildfarm member produce the above logs? Many buildfarm
> > members failed with that error due to commit 6a80179f6b0, but I've not
> > seen further failures since pushing commit 18f9785e0b3.
>
> Ah, you are right, there are no failures later than 6aba42c.  I was
> misled by the fact that several of the complaining animals are still
> red because they've not run since then.  Sorry for the noise.

No problem, thank you for the confirmation.

I've confirmed that the fix made the buildfarm green again, so I've
marked this open item as resolved.

Regards,

--
Masahiko Sawada
Amazon Web Services: https://aws.amazon.com
Attachment

pgsql-hackers by date:

Previous
From: Japin Li
Date:
Subject: Re: WAL compression setting after PostgreSQL LZ4 default change
Next
From: Peter Geoghegan
Date:
Subject: GiST multirange index scans can fail to return rows