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

From: "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>
To: 'Masahiko Sawada' <sawada(dot)mshk(at)gmail(dot)com>
Cc: Alexander Lakhin <exclusion(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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-11-03 04:20:03
Message-ID: OS7PR01MB183176018F4AA48A2DB89E194F5692@OS7PR01MB18317.jpnprd01.prod.outlook.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Sawada-san,

> The 0001 patch basically looks good to me. Is there any reason that
> the patch sets "verbose => 0" to some query_safe() calls? Also, I'd
> suggest renaming the support function to quit_and_wait().

I just tried to suppress output, not mandatory. PSA fixed version.
I fixed 0001 as well.

> I'll review the 0003 patch soon.

Thanks!

Best regards,
Hayato Kuroda
FUJITSU LIMITED

Attachment Content-Type Size
v3-0001-Stabilize-051_effective_wal_level.patch application/octet-stream 6.0 KB
v3-0002-Ensure-injection-point-repack-concurrently-before.patch application/octet-stream 1.3 KB
v3-0003-Stabilize-010_index_concurrently_upsert.patch application/octet-stream 6.1 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Ajin Cherian 2026-11-03 04:25:33 Re: [PATCH] Preserve replication origin OIDs in pg_upgrade
Previous Message shihao zhong 2026-11-03 04:08:17 Re: Hash index corruption and CLOG lookup errors from checkpoint races