Re: Fix "unexpected logical decoding status change" error; from concurrent logical decoding activation

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
Cc: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Srinath Reddy Sadipiralla <srinath2133(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Fix "unexpected logical decoding status change" error; from concurrent logical decoding activation
Date: 2026-07-31 04:00:51
Message-ID: 1727220.1785470451@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> writes:
> On Thu, Jul 30, 2026 at 5:52 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Davis 2026-07-31 04:20:06 Re: CREATE SUBSCRIPTION ... SERVER vs. pg_dump, etc.
Previous Message Tristan Partin 2026-07-31 03:54:33 Re: Increase repalloc_array() usage in buffile.c