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

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
Cc: 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-23 11:43:07
Message-ID: CAA4eK1K+eQuqiNJp3KrQS3+yGYUdCWMKLLet3DrwU+cWOFj6FA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jul 16, 2026 at 6:52 AM Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> wrote:
>
> 0001 is the fix for the originally reported issue, unchanged from the
> previous version.
>

0001 LGTM. This is a separate fix than 0002, so we can proceed with
the commit of this one unless you want to combine the fix for both the
issues and want to make a single commit.

--
With Regards,
Amit Kapila.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jim Jones 2026-07-23 11:51:22 Re: COMMENTS are not being copied in CREATE TABLE LIKE
Previous Message John Naylor 2026-07-23 11:09:13 Re: Fix missing FORMAT when deparsing JSON_ARRAY(query)