Re: Allow specifying a dbname in pg_basebackup connection string

From: Jelte Fennema <me(at)jeltef(dot)nl>
To: Jim Jones <jim(dot)jones(at)uni-muenster(dot)de>
Cc: Tristen Raab <tristen(dot)raab(at)highgo(dot)ca>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Jelte Fennema <github-tech(at)jeltef(dot)nl>
Subject: Re: Allow specifying a dbname in pg_basebackup connection string
Date: 2023-08-30 12:11:07
Message-ID: CAGECzQSqBfLS9D_DvUA5=bJeVaeWFAT2TOvjBNW8tVpAfXAAPg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, 30 Aug 2023 at 01:01, Jim Jones <jim(dot)jones(at)uni-muenster(dot)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.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2023-08-30 12:16:47 Re: lockup in parallel hash join on dikkop (freebsd 14.0-current)
Previous Message Aleksander Alekseev 2023-08-30 12:10:20 Re: New compiler warning