Horton

Re: Allow specifying a dbname in pg_basebackup connection string

Jelte Fennema <me@jeltef.nl>

View thread View on postgr.es
From: Jelte Fennema <me@jeltef.nl>
To: Jim Jones <jim.jones@uni-muenster.de>
Cc: Tristen Raab <tristen.raab@highgo.ca>, pgsql-hackers@lists.postgresql.org, Jelte Fennema <github-tech@jeltef.nl>
Date: 2023-08-30T12:11:07Z
Lists: pgsql-hackers 
On Wed, 30 Aug 2023 at 01:01, Jim Jones <jim.jones@uni-muenster.de> wrote:
> However, pgbouncer closes with a segmentation fault, so I couldn't test the result of pg_basebackup itself - but I guess it isn't the issue here.

Oops it indeed seemed like I made an unintended change when handling
database names that did not exist in pgbouncer.conf when you used
auth_type=hba. I pushed a fix for that now to the replication-support
branch. Feel free to try again. But as you said it's unrelated to the
postgres patch.

Commits

  1. pg_basebackup, pg_receivewal: fix failure to find password in ~/.pgpass.

  2. Allow dbname in pg_basebackup/pg_receivewal connstring