public inbox for [email protected]
help / color / mirror / Atom feedFrom: Fujii Masao <[email protected]>
To: Masahiko Sawada <[email protected]>
Cc: Amit Kapila <[email protected]>
Cc: Bharath Rupireddy <[email protected]>
Cc: PostgreSQL-development <[email protected]>
Subject: Re: Add a hook for handling logical decoding messages on subscribers.
Date: Thu, 9 Jul 2026 21:14:46 +0900
Message-ID: <CAHGQGwELqH7P8PBOGE2-un8qC_oQpT2jOgbPsAjK6YA5dnbKWQ@mail.gmail.com> (raw)
In-Reply-To: <CAD21AoATy+CzYmNYp_fKi4zsGLEGOmZen3OR+hxsCqn2GsQBoQ@mail.gmail.com>
References: <CAD21AoCTNGiddikkUcDKj5QLnsg-51bpr-o6L-GTHWZL4ZFYtQ@mail.gmail.com>
<CALj2ACXLkU4y+mmk2gHzmvSV4KTishSe=HhZ_yn=NHFBDGrwFQ@mail.gmail.com>
<CAA4eK1JC9+R4S7L7y3DazOOMpnANVyCpsx84RSYjX6vfxLdK6w@mail.gmail.com>
<CAD21AoATy+CzYmNYp_fKi4zsGLEGOmZen3OR+hxsCqn2GsQBoQ@mail.gmail.com>
On Wed, Jun 24, 2026 at 3:02 AM Masahiko Sawada <[email protected]> wrote:
> Right. I'm implementing a basic DDL replication solution using this
> hook as a sample implementation. Other than that, this feature can be
> used to add additional information for the replicated transaction that
> is not replicated via logical replication protocol, such as the
> executed user or context-specific information, which can then be
> dispatched to a CDC system connected to the subscriber.
+1 for the proposed hook, although I haven't read the patch yet.
I know of a system that uses logical decoding messages to propagate data
to external systems. In that system, the application writes the data to
be propagated as logical decoding messages, and a CDC pipeline consumes
them via logical decoding and sends them to other systems, for example
through Kafka.
In that system, when the remote site is maintained by physical replication,
the same logical decoding messages can be decoded on the standby
at the remote site to deliver them to external systems there. However,
if the remote site uses logical replication instead, those messages are
currently neither delivered to nor processed on the subscriber at
the remote site. As a result, the CDC pipeline at the remote site cannot
consume the data they carry.
The proposed hook might be useful for this use case. An extension could
process the incoming logical decoding messages on the subscriber and
forward them to the local CDC pipeline, or store or re-emit them in a form
that local consumers can process.
Regards,
--
Fujii Masao
view thread (7+ messages)
reply
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: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected]
Subject: Re: Add a hook for handling logical decoding messages on subscribers.
In-Reply-To: <CAHGQGwELqH7P8PBOGE2-un8qC_oQpT2jOgbPsAjK6YA5dnbKWQ@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox