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 CAD21AoCTWJLMEqcDBk83108daYdAoU_KLTMsgWwJ5WLO3BUm0g@mail.gmail.com
Whole thread
In response to Re: Fix "unexpected logical decoding status change" error; from concurrent logical decoding activation  (Nisha Moond <nisha.moond412@gmail.com>)
Responses Re: Fix "unexpected logical decoding status change" error; from concurrent logical decoding activation
List pgsql-hackers
On Thu, Oct 1, 2026 at 4:08 AM Nisha Moond <nisha.moond412@gmail.com> wrote:
>
> On Sat, Sep 26, 2026 at 3:54 AM Masahiko Sawada <sawada.mshk@gmail.com> wrote:
> >
> >
> > I've incorporated your comment suggestions, and updated cosmetic
> > things.Please review them.
> >
>
> Hi,
> I reviewed the TAP test and it LGTM. I found no correctness issues,
> just a couple of nits compared to the neighboring tests. Please
> consider these if they look okay to you:
>
> 1) Add the sync_slot condition to injection_points_attach() similar to
> the neighboring tests, so the wait happens only when sync_slot itself
> is being created.
> 2) Add a note() after wait_for_event(), as in the other tests, so the
> test output shows when the sync is paused at the injection point.
>

Both suggestions look good to me. I've incorporated these suggestions
and updated the comment as discussed with Amit. I've attached the
updated patch.

Regards,

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

Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: WAL segment file descriptor leak on read errors can PANIC the server
Next
From: Michael Paquier
Date:
Subject: Re: WAL segment file descriptor leak on read errors can PANIC the server