| From: | Ajin Cherian <itsajin(at)gmail(dot)com> |
|---|---|
| To: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
| Cc: | robertmhaas(at)gmail(dot)com, kuroda(dot)hayato(at)fujitsu(dot)com, barwick(at)gmail(dot)com, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Have pg_basebackup write "dbname" in "primary_conninfo"? |
| Date: | 2024-02-21 03:41:59 |
| Message-ID: | CAFPTHDbreMtLnQDrqJOG8+a+X+x=CkQOt9NM-ScpHz_LMCZ-jA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Feb 21, 2024 at 2:04 PM Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
wrote:
>
> Although I haven't looked the original thread, it seems that the
> dbname is used only by pg_sync_replication_slots(). If it is true,
> couldn't we make the SQL function require a database name to make a
> connection, instead of requiring it in physical-replication conninfo?
>
>
>
In the original thread, the intention is to not just provide this
functionality using the function pg_sync_replication_slots(), but provide
a GUC option on standbys to sync logical replication slots periodically
even without calling that function. This requires connecting to a database.
regards,
Ajin Cherian
Fujitsu Australia
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bharath Rupireddy | 2024-02-21 04:19:37 | Re: Add lookup table for replication slot invalidation causes |
| Previous Message | Ajin Cherian | 2024-02-21 03:37:21 | Re: Have pg_basebackup write "dbname" in "primary_conninfo"? |