| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com> |
| Cc: | Ian Lawrence Barwick <barwick(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Have pg_basebackup write "dbname" in "primary_conninfo"? |
| Date: | 2024-02-20 11:06:09 |
| Message-ID: | CA+TgmoYfagyp5AvKMfGpRUgXNJZ0ymuqiWTzOc2tV_ZMM0UkCA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Feb 20, 2024 at 4:18 PM Hayato Kuroda (Fujitsu)
<kuroda(dot)hayato(at)fujitsu(dot)com> wrote:
> I found an inconsistency. When I ran ` pg_basebackup -D data_N2 -U postgres -R`,
> dbname would be set as username.
>
> ```
> primary_conninfo = 'user=postgres ... dbname=postgres
> ```
>
> However, when I ran `pg_basebackup -D data_N2 -d "user=postgres" -R`,
> dbname would be set as "replication". Is it an intentional item?
>
> ```
> primary_conninfo = 'user=postgres ... dbname=replication...
> ```
Seems weird to me. You don't use dbname=replication to ask for a
replication connection, so why would we ever end up with that
anywhere? And especially in only one of two such closely related
cases?
--
Robert Haas
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bharath Rupireddy | 2024-02-20 11:10:44 | Add lookup table for replication slot invalidation causes |
| Previous Message | Matthias van de Meent | 2024-02-20 11:02:41 | Re: Add bump memory context type and use it for tuplesorts |