Skip to content

docs: pgbouncer for postgresql replica #1217

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs: pgbouncer for postgresql replica #1217

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions docs/user-guide/additional-services/pgbouncer.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -92,6 +92,13 @@ Noteworthy default configuration:
- `auth_file` should not be changed.
- `pidfile` should not be changed.

### PgBouncer for PostgreSQL replica

You may want to point your read-only queries towards the PostgreSQL replica to offload the PostgreSQL master.
To do this with PgBouncer we can install a separate PgBouncer Deployment that connects to the replica.
This Deployment is configured separately, the ConfigMap and Secret for this Deployment contain `pgbouncer-repl`, e.g. `cluster-name-pgbouncer-repl-config` and `cluster-name-pgbouncer-repl-auth-file` respectively.
This separate PgBouncer Deployment is disabled by default to avoid taking up unnecessary resources if unused, but can be enabled by filing a service ticket.

## Migration for application developers

Follow these steps if you as an application developer already use the Managed PostgreSQL offering and want to start using Managed PgBouncer.
Expand Down