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 CAD21AoCZY1fKYgfkvHGWGiXpatUKd23FSLnDCL4m9bWFjdXNZw@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: Proposal: Conflict log history table for Logical Replication
List pgsql-hackers
On Thu, Jul 30, 2026 at 2:00 AM Amit Kapila <amit.kapila16@gmail.com> wrote:
>
> On Thu, Jul 30, 2026 at 12:37 PM Masahiko Sawada <sawada.mshk@gmail.com> wrote:
> >
> > Thank you for testing it. It seems to be reproducible also on CI, and
> > I believe I've fixed the issue.
> >
> > I've attached the patch. Please review it.
> >
>
> LGTM.

Thank you for reviewing the patch. Pushed.

... but some buildfarm members are unhappy. I'm working on it.

Regards,

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



pgsql-hackers by date:

Previous
From: David K
Date:
Subject: Re: Bug: XLogReader mishandles oversized multi-page xl_tot_len (potential memory corruption)
Next
From: shveta malik
Date:
Subject: Re: Support EXCEPT for TABLES IN SCHEMA publications