Re: Check for existing replication slot in pg_createsubscriber

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: Zane Duffield <duffieldzane(at)gmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Check for existing replication slot in pg_createsubscriber
Date: 2025-06-30 03:01:42
Message-ID: CAA4eK1+nEH9ZaeL+gLxnovpLL8945W6wnnyaafE=YLJNLmYD=Q@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Jun 27, 2025 at 1:13 PM Zane Duffield <duffieldzane(at)gmail(dot)com> wrote:
>
> Hackers,
>
> I noticed in testing and usage that pg_createsubscriber doesn't check for an existing replication slot before attempting to create one, whereas it *does* check for existing publications.
>

I see the difference you are pointing to. Ideally, the checks should
be the same unless there is a specific reason for them to be
different, which should be mentioned in the comments. BTW, do you see
any problems due to name conflicts while using this tool, or is it a
code-level observation? AFAICS, the names for the objects created by
pg_subscriber are either generated names (with an intention that it
doesn't conflict) or user-provided. In both cases, chances should be
less that they conflict with existing objects.

--
With Regards,
Amit Kapila.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Zane Duffield 2025-06-30 03:07:40 Re: Check for existing replication slot in pg_createsubscriber
Previous Message Tender Wang 2025-06-30 02:38:46 Re: MergeJoin beats HashJoin in the case of multiple hash clauses