From: Michael Paquier <michael@paquier.xyz>
To: Haiyang Li <mohen.lhy@alibaba-inc.com>
Cc: Xuneng Zhou <xunengzhou@gmail.com>
Cc: pgsql-bugs <pgsql-bugs@lists.postgresql.org>
Subject: Re: BUG #19109: catalog lookup with the wrong snapshot during logical decoding causes coredump
Date: Tue, 11 Nov 2025 11:12:17 +0900
Message-ID: <aRKbgWylZllp4vYF@paquier.xyz> (raw)
In-Reply-To: <13b5ed51-0a02-4b3a-b8b3-b33505f1fe6c.mohen.lhy@alibaba-inc.com>
References: <19109-4a9ce36715d69632@postgresql.org>
<CABPTF7W883TcGrY71vVDTdEJgxJ993_Fe+fHTT+1Ttk6oDH3YQ@mail.gmail.com>
<13b5ed51-0a02-4b3a-b8b3-b33505f1fe6c.mohen.lhy@alibaba-inc.com>
On Tue, Nov 11, 2025 at 09:42:29AM +0800, Haiyang Li wrote:
> The WAL are provided in attachment. Unfortunately, I can not share the script.
> The testing scenario is rather complex, and the executed SQL statements can
> only be tracked via the logs. At this point, I have not been able to obtain a
> reproducible case, which is the challenging part. However, I can provide the
> actions carried out by a specific transaction if you need.
That's unfortunate. Having a reproducible test case that works with
upstream would speed up the analysis of the problem a lot.
--
Michael
Attachments:
[application/pgp-signature] signature.asc (832B, ../aRKbgWylZllp4vYF@paquier.xyz/2-signature.asc)
download
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 using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: michael@paquier.xyz, mohen.lhy@alibaba-inc.com, xunengzhou@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #19109: catalog lookup with the wrong snapshot during logical decoding causes coredump
In-Reply-To: <aRKbgWylZllp4vYF@paquier.xyz>
* 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