Re: Allow using replication origins in SQL level parallel sessions

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: emre(at)hasegeli(dot)com
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Allow using replication origins in SQL level parallel sessions
Date: 2025-09-05 11:25:43
Message-ID: CAA4eK1KJSMWtTXdMs36FcPt7tkMAGkcA8o1FU_jL32GvMkU-7g@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Sep 4, 2025 at 11:32 PM Emre Hasegeli <emre(at)hasegeli(dot)com> wrote:
>
> Replication origins is a useful feature for external replication
> systems to do conflict resolution in bi-directional replication. It's
> possible for the external systems to make use of this feature using
> the SQL functions pg_replication_origin_*().
>
> pg_replication_origin_session_setup() is the one to configure the
> current session. Currently, only a single version of this function is
> exposed that allows one replica origin to be used only by a single
> session. This limits the usefulness of this feature.
>
> The attached patch creates another variant of this function
> pg_replication_origin_session_setup(text, int). This allows the same
> replica origin to be used by parallel sessions the same way logical
> replication apply workers are using it.
>

We are already discussing the same feature in an email thread [1]. Can
you check that and share your inputs there?

[1] - https://www.postgresql.org/message-id/CAMPB6wfe4zLjJL8jiZV5kjjpwBM2%3DrTRme0UCL7Ra4L8MTVdOg%40mail.gmail.com

--
With Regards,
Amit Kapila.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Ashutosh Bapat 2025-09-05 11:27:34 Re: [Proposal] Expose internal MultiXact member count function for efficient monitoring
Previous Message Amit Kapila 2025-09-05 11:20:06 Re: Logical Replication of sequences