Re: Check for existing replication slot in pg_createsubscriber
От | Amit Kapila |
---|---|
Тема | Re: Check for existing replication slot in pg_createsubscriber |
Дата | |
Msg-id | CAA4eK1+nEH9ZaeL+gLxnovpLL8945W6wnnyaafE=YLJNLmYD=Q@mail.gmail.com обсуждение исходный текст |
Ответ на | Check for existing replication slot in pg_createsubscriber (Zane Duffield <duffieldzane@gmail.com>) |
Ответы |
Re: Check for existing replication slot in pg_createsubscriber
|
Список | pgsql-hackers |
On Fri, Jun 27, 2025 at 1:13 PM Zane Duffield <duffieldzane@gmail.com> wrote: > > Hackers, > > I noticed in testing and usage that pg_createsubscriber doesn't check for an existing replication slot before attemptingto 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.
В списке pgsql-hackers по дате отправления: