Re: Allow specifying a dbname in pg_basebackup connection string - Mailing list pgsql-hackers

From Jelte Fennema
Subject Re: Allow specifying a dbname in pg_basebackup connection string
Date
Msg-id CAGECzQSv_zXsjTGhDMQW3Z3fHBzorg6as5ojJjLAO2wQrGuurg@mail.gmail.com
Whole thread Raw
In response to Re: Allow specifying a dbname in pg_basebackup connection string  ("Euler Taveira" <euler@eulerto.com>)
Responses Re: Allow specifying a dbname in pg_basebackup connection string
List pgsql-hackers
On Wed, 5 Jul 2023 at 16:01, Euler Taveira <euler@eulerto.com> wrote:
> 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.

Indeed the transparent proxy use case is where replication through
pgbouncer makes sense. There's quite some reasons to set up PgBouncer
like such a proxy apart from security policies. Some others that come
to mind are:
- load balancer layer of pgbouncers
- transparent failovers
- transparent database moves

And in all of those cases its nice for a user to use a single
connection string/hostname. Instead of having to think: Oh yeah, for
backups, I need to use this other one.



pgsql-hackers by date:

Previous
From: Ashutosh Bapat
Date:
Subject: Re: logical decoding and replication of sequences, take 2
Next
From: Matthias van de Meent
Date:
Subject: Re: [PATCH] Add GitLab CI to PostgreSQL