| From: | "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com> |
|---|---|
| To: | 'Amit Kapila' <amit(dot)kapila16(at)gmail(dot)com>, Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com> |
| Cc: | 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-02 10:01:07 |
| Message-ID: | OS9PR01MB12149561C881BFA9DFB10B149F5122@OS9PR01MB12149.jpnprd01.prod.outlook.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
Best regards,
Hayato Kuroda
FUJITSU LIMITED
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jakub Wartak | 2026-06-02 10:13:09 | Re: Heads Up: cirrus-ci is shutting down June 1st |
| Previous Message | solai v | 2026-06-02 09:42:10 | Re: problems with toast.* reloptions |