On Wed, 5 Jul 2023 at 16:50, Jelte Fennema <postgres@jeltef.nl> wrote:
>
> 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.
Okay, understood. In that case, please remember to write changes to
the pg_basebackup docs page explaining how the dbname value is ignored
under normal usage.
Thom