Re: Allow specifying a dbname in pg_basebackup connection string
Euler Taveira <euler@eulerto.com>
From: "Euler Taveira" <euler@eulerto.com>
To: "Thom Brown" <thom@linux.com>, "Jelte Fennema" <postgres@jeltef.nl>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2023-07-05T14:01:08Z
Lists: pgsql-hackers
On Wed, Jul 5, 2023, at 9:43 AM, Thom Brown wrote: > I guess my immediate question is, should backups be taken through > PgBouncer? It seems beyond PgBouncer's remit. One of the PgBouncer's missions is to be a transparent proxy. Sometimes you cannot reach out the database directly due to a security policy. I've heard this backup question a few times. IMO if dbname doesn't matter for reaching the server directly, I don't see a problem relaxing this restriction to support this use case. We just need to document that dbname will be ignored if specified. Other connection poolers might also benefit from it. -- Euler Taveira EDB https://www.enterprisedb.com/
Commits
-
pg_basebackup, pg_receivewal: fix failure to find password in ~/.pgpass.
- b1008c1f01ff 18.0 landed
- e2a912909308 17.1 landed
-
Allow dbname in pg_basebackup/pg_receivewal connstring
- cca97ce6a665 17.0 landed