Re: Have pg_basebackup write "dbname" in "primary_conninfo"? - Mailing list pgsql-hackers

From Ajin Cherian
Subject Re: Have pg_basebackup write "dbname" in "primary_conninfo"?
Date
Msg-id CAFPTHDbreMtLnQDrqJOG8+a+X+x=CkQOt9NM-ScpHz_LMCZ-jA@mail.gmail.com
Whole thread Raw
In response to Re: Have pg_basebackup write "dbname" in "primary_conninfo"?  (Kyotaro Horiguchi <horikyota.ntt@gmail.com>)
List pgsql-hackers


On Wed, Feb 21, 2024 at 2:04 PM Kyotaro Horiguchi <horikyota.ntt@gmail.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

pgsql-hackers by date:

Previous
From: Ajin Cherian
Date:
Subject: Re: Have pg_basebackup write "dbname" in "primary_conninfo"?
Next
From: Bharath Rupireddy
Date:
Subject: Re: Add lookup table for replication slot invalidation causes