| From: | Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com> |
|---|---|
| To: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
| Cc: | Zhijie Hou <houzhijie22(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Add a hook for handling logical decoding messages on subscribers. |
| Date: | 2026-11-17 08:14:30 |
| Message-ID: | avwM5nLKh0lApeKU@bdtpg |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On Mon, Nov 16, 2026 at 11:05:00AM -0800, Masahiko Sawada wrote:
>
> I've attached the updated patches.
Thanks!
I did not look in details but I have a question. I'm wondering what would happen
with an unpatched publisher when both messages and streaming are enabled. Suppose
a message is emitted in a subtransaction that is later aborted. The publisher
sends the top level XID with the message, whereas STREAM ABORT refers to the
subtransaction XID. IIUC, the patched subscriber would therefore not discard that
message.
Should 0002 handle this case somehow?
Regards,
--
Bertrand Drouvot
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jingtang Zhang | 2026-11-17 08:17:37 | Re: transaction_timeout is not enforced during ClientWrite |
| Previous Message | Jim Jones | 2026-11-17 08:09:19 | Re: ISBN range table |