| From: | Jelte Fennema <postgres(at)jeltef(dot)nl> |
|---|---|
| To: | Euler Taveira <euler(at)eulerto(dot)com> |
| Cc: | Thom Brown <thom(at)linux(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Allow specifying a dbname in pg_basebackup connection string |
| Date: | 2023-07-05 15:50:01 |
| Message-ID: | CAGECzQSv_zXsjTGhDMQW3Z3fHBzorg6as5ojJjLAO2wQrGuurg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 5 Jul 2023 at 16:01, Euler Taveira <euler(at)eulerto(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matthias van de Meent | 2023-07-05 15:58:34 | Re: [PATCH] Add GitLab CI to PostgreSQL |
| Previous Message | Ashutosh Bapat | 2023-07-05 14:54:34 | Re: logical decoding and replication of sequences, take 2 |