| From: | Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com> |
|---|---|
| To: | "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com> |
| Cc: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Shubham Khanna <khannashubham1197(at)gmail(dot)com> |
| Subject: | Re: pg_createsubscriber: allow duplicate publication names |
| Date: | 2026-06-03 02:25:28 |
| Message-ID: | D5096ECC-26CE-4C83-BBFA-A025CFA50DA9@gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On Jun 2, 2026, at 18:01, Hayato Kuroda (Fujitsu) <kuroda(dot)hayato(at)fujitsu(dot)com> wrote:
>
> Dear Amit,
>
>> Can't we use --replication-slot=name to avoid this ERROR? I mean use
>> different replication slot names.
>
> Are you saying the below case, right? It can work.
>
> ```
> $ pg_createsubscriber -D data_sta/ -P 'user=postgres port=5432' -d postgres --subscription sub --replication-slot=slot1 -d testdb --subscription sub --replication-slot=slot2 -U postgres
> ```
>
> BTW; slot creations are tried before the standby promotes, thus there may be a chance
> user read the error message, change the subscription name, and retry. But I still
> think we should guard the combination, which means it's too late for PG19.
>
Hi Hayato-san, thanks for the comment. I’ll keep it in my notes for later reference.
BTW, I just saw someone has added this patch to the Open Items list.
Best regards,
--
Chao Li (Evan)
HighGo Software Co., Ltd.
https://www.highgo.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | wenhui qiu | 2026-06-03 02:32:07 | Re: Report oldest xmin source when autovacuum cannot remove tuples |
| Previous Message | Michael Paquier | 2026-06-03 02:21:52 | Re: Fix DROP PROPERTY GRAPH "unsupported object class" error |