pg.ddx.io pgsql-hackers@postgresql.org mailing list archivehelp / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Masahiko Sawada <sawada.mshk@gmail.com>
Cc: Amit Kapila <amit.kapila16@gmail.com>
Cc: Srinath Reddy Sadipiralla <srinath2133@gmail.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: Fix "unexpected logical decoding status change" error; from concurrent logical decoding activation
Date: Thu, 30 Jul 2026 20:52:46 -0400
Message-ID: <1714235.1785459166@sss.pgh.pa.us> (raw)
In-Reply-To: <CAD21AoDFpgsqN0b0tyg6iLJ=F7ntYua_2y6x4UUfk9WQu3WBsA@mail.gmail.com>
References: <CAFC+b6oYzmAgp7F0ivrhfZT46-CjvCTrU9pWuMNcem-52YjOTw@mail.gmail.com>
<CAFC+b6rD3c9-s0ZcodAeJB+UTYTV4tPzrgLzJzzDj0QYuBGZJQ@mail.gmail.com>
<CAD21AoA_pRC3UOz_x9-iL65V9b5NVVRbcDtJ6MamfnN3ZA0n_Q@mail.gmail.com>
<CAD21AoDEB99VtNbQdDrNd=1gQupJNGMfW_5kdnxq03Q82EK3ag@mail.gmail.com>
<CAA4eK1K+eQuqiNJp3KrQS3+yGYUdCWMKLLet3DrwU+cWOFj6FA@mail.gmail.com>
<CAD21AoAxyQHgwWg4udS1_KhuECEWyNkOsh+jODNyj66gjqV4Ug@mail.gmail.com>
<CAA4eK1KRwzSOvNuJ8FVFYzzp4L3uUf_Z_iHDbmnT2pG6y6nfwQ@mail.gmail.com>
<CAD21AoBZGuDVa-ctuko+Oma+X9qYppQbzWo8gNmJ1AiRyAjq7g@mail.gmail.com>
<CAA4eK1+=spL_j76yVvfx5ZObwxfgg6tNWSQbL+84jHqNKGTP6A@mail.gmail.com>
<CAD21AoCZY1fKYgfkvHGWGiXpatUKd23FSLnDCL4m9bWFjdXNZw@mail.gmail.com>
<CAD21AoDFpgsqN0b0tyg6iLJ=F7ntYua_2y6x4UUfk9WQu3WBsA@mail.gmail.com>
Masahiko Sawada <sawada.mshk@gmail.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
view thread (59+ messages) latest in thread
Message-ID: <1714235.1785459166@sss.pgh.pa.us> Permalink: ../1714235.1785459166@sss.pgh.pa.us/ Also on: postgresql.org/message-id/1714235.1785459166@sss.pgh.pa.us ·
reply
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Reply to all the recipients from your mail client; the link fills in the headers below: reply via email Some clients, webmail especially, drop In-Reply-To and References from a link, and the reply then starts a new thread: use the mbox below. To: pgsql-hackers@postgresql.org Cc: tgl@sss.pgh.pa.us, sawada.mshk@gmail.com, amit.kapila16@gmail.com, srinath2133@gmail.com Subject: Re: Fix "unexpected logical decoding status change" error; from concurrent logical decoding activation In-Reply-To: <1714235.1785459166@sss.pgh.pa.us> References: <CAFC+b6oYzmAgp7F0ivrhfZT46-CjvCTrU9pWuMNcem-52YjOTw@mail.gmail.com> <CAFC+b6rD3c9-s0ZcodAeJB+UTYTV4tPzrgLzJzzDj0QYuBGZJQ@mail.gmail.com> <CAD21AoA_pRC3UOz_x9-iL65V9b5NVVRbcDtJ6MamfnN3ZA0n_Q@mail.gmail.com> <CAD21AoDEB99VtNbQdDrNd=1gQupJNGMfW_5kdnxq03Q82EK3ag@mail.gmail.com> <CAA4eK1K+eQuqiNJp3KrQS3+yGYUdCWMKLLet3DrwU+cWOFj6FA@mail.gmail.com> <CAD21AoAxyQHgwWg4udS1_KhuECEWyNkOsh+jODNyj66gjqV4Ug@mail.gmail.com> <CAA4eK1KRwzSOvNuJ8FVFYzzp4L3uUf_Z_iHDbmnT2pG6y6nfwQ@mail.gmail.com> <CAD21AoBZGuDVa-ctuko+Oma+X9qYppQbzWo8gNmJ1AiRyAjq7g@mail.gmail.com> <CAA4eK1+=spL_j76yVvfx5ZObwxfgg6tNWSQbL+84jHqNKGTP6A@mail.gmail.com> <CAD21AoCZY1fKYgfkvHGWGiXpatUKd23FSLnDCL4m9bWFjdXNZw@mail.gmail.com> <CAD21AoDFpgsqN0b0tyg6iLJ=F7ntYua_2y6x4UUfk9WQu3WBsA@mail.gmail.com> <1714235.1785459166@sss.pgh.pa.us> * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions for how to clone and mirror all data and code used for this inbox