Re: [Patch] add new parameter to pg_replication_origin_session_setup - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: [Patch] add new parameter to pg_replication_origin_session_setup
Date
Msg-id CAA4eK1JgkWgg3hfxSPsOgtamh4sgWLFQqYFL_oEhqHgtHhJriA@mail.gmail.com
Whole thread
In response to Re: [Patch] add new parameter to pg_replication_origin_session_setup  (Amit Kapila <amit.kapila16@gmail.com>)
Responses Re: [Patch] add new parameter to pg_replication_origin_session_setup
List pgsql-hackers
On Wed, Feb 11, 2026 at 10:53 AM Amit Kapila <amit.kapila16@gmail.com> wrote:
>
> On Wed, Feb 4, 2026 at 12:38 AM Heikki Linnakangas <hlinnaka@iki.fi> wrote:
> >
> > The new error message is not great:
> >
> > postgres=# select pg_replication_origin_session_setup('myorigin', 12345678);
> > ERROR:  could not find replication state slot for replication origin
> > with OID 1 which was acquired by 12345678
> >
> > Firstly, replication origin is not an OID. Secondly, it's a little
> > confusing because the "replication state slot" is in fact present.
> > However, it's currently inactive, i.e. not "acquired" by the given PID.
> >
> > I propose to change that to:
> >
> > postgres=# select pg_replication_origin_session_setup('myorigin', 12345678);
> > ERROR:  replication origin with ID 1 is not active for PID 12345678
> >
> > That's more in line with this neighboring message:
> >
> > ERROR:  replication origin with ID 1 is already active for PID 701228
> >
>
> +1 for the new message.
>

Heikki, would you like to take care of improvements proposed by you?
Otherwise, I am happy to take care of them.

--
With Regards,
Amit Kapila.



pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: Add a greedy join search algorithm to handle large join problems
Next
From: Bertrand Drouvot
Date:
Subject: Re: rename and move AssertVariableIsOfType