Re: Check for existing replication slot in pg_createsubscriber

From: Zane Duffield <duffieldzane(at)gmail(dot)com>
To: Amit Kapila <amit(dot)kapila16(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:07:40
Message-ID: CACMiCkVn0NTsXRXj9bNGKDQPPPr_GQ8tB2qCPSxF5s1tGcrU-g@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jun 30, 2025 at 1:01 PM Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:

>
> 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?

In my case the --subscription and --replication-slot options are used to
control the identifiers; the conflict was the user's fault, not the
program's.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2025-06-30 03:15:29 Re: Check for existing replication slot in pg_createsubscriber
Previous Message Amit Kapila 2025-06-30 03:01:42 Re: Check for existing replication slot in pg_createsubscriber