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 00:52:46
Message-ID: 1714235.1785459166@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:
> I've reproduced the issue on local and confirmed the root cause; two
> background psql sessions in the TAP test run with ON_ERROR_STOP=1 and
> got canceled by pg_cancel_backend(), so psql exited as soon as the
> cancelation error arrived. I've attached the patch that fixes the
> problem. I'm waiting for CI to check if the tests still pass on other
> environments.

The buildfarm looks like this has made 051_effective_wal_level.pl
less stable, not more so. The failures all look like

[18:37:44.952](0.014s) # injection_point 'logical-decoding-activation' is reached
[18:37:44.982](0.030s) ok 35 - the activation process aborted
[18:37:44.982](0.001s) # die: ack Broken pipe: write( 13, '\\q
# ' ) at /usr/share/perl5/vendor_perl/IPC/Run/IO.pm line 550.
[18:37:44.982](0.000s) 1..35
ack Broken pipe: write( 13, '\\q
' ) at /usr/share/perl5/vendor_perl/IPC/Run/IO.pm line 550.
# Postmaster PID for node "primary" is 81208
### Stopping node "primary" using mode immediate

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Ian Lawrence Barwick 2026-07-31 00:58:02 Re: [PATCH] Add pg_get_event_trigger_ddl() function
Previous Message Tom Lane 2026-07-30 23:57:52 Re: zic: fix PostgreSQL build failure on filesystems without hard link support