| From: | Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com> |
|---|---|
| To: | "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Subject: | Re: pg_createsubscriber: allow duplicate subscription names |
| Date: | 2026-08-06 08:36:36 |
| Message-ID: | 59AFF62A-A206-4513-9B50-908E1FEA392C@gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On Aug 6, 2026, at 15:09, Hayato Kuroda (Fujitsu) <kuroda(dot)hayato(at)fujitsu(dot)com> wrote:
>
> Dear Chao,
>
> Thanks for working on it. I checked your patch and briefly looks good.
Thank you very much for reviewing the patch.
>
> ```
> + if (duplicate_sub_name && num_replslots == 0)
> + {
> + pg_log_error("duplicate subscription names require distinct replication slot names");
> + pg_log_error_detail("When replication slot names are not specified, subscription names are used, but replication slot names must be unique within a cluster.");
> + pg_log_error_hint("Specify a unique --replication-slot name for each database.");
> + exit(1);
> + }
> ```
>
> Not sure pg_log_error_detail() is helpful here. Can we remove?
I thought to provide more info, maybe too verbose.
> Also I feel we do not have to clarify "distinct/unique" for replication slot names,
> it has already been described other lines.
Okay, removed.
PFA v2 - addressed Hayato-san’s comments.
Best regards,
--
Chao Li (Evan)
HighGo Software Co., Ltd.
https://www.highgo.com/
| Attachment | Content-Type | Size |
|---|---|---|
| v2-0001-pg_createsubscriber-Allow-duplicate-subscription-.patch | application/octet-stream | 5.3 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2026-08-06 08:37:46 | Re: convert various variables to atomics |
| Previous Message | David Rowley | 2026-08-06 08:29:28 | Re: [PATCH] Use ssup_datum_*_cmp for int2, oid, and oid8 sort support |