sincecutoff.com
← all changes

Railway Postgres PgBouncer management

Introduced 2026-08-08 · score 0.93

HOW TO USE IT

When managing PgBouncer for a Postgres service, use `railway postgres pgbouncer` with the relevant subcommand; selectors targeting a PgBouncer or HAProxy edge resolve to the database root. Configure requires at least one setting, and its warnings are advisory per the release note.

railway postgres pgbouncer status --service <postgres-service>
railway postgres pgbouncer add --service <postgres-service> --pool-mode transaction
railway postgres pgbouncer configure --service <postgres-service> --max-client-conn 200

WHY THIS HELPS

Inspect or change PgBouncer configuration, pool mode, regional replica count, or service presence for a Postgres deployment.

REQUIREMENTS AND LIMITATIONS

  • Version: v5.33.0
  • --service <service>: Select the service; edge-node selectors resolve to the database root. The documented examples use `--service postgres`.
  • --pool-mode <transaction|session|statement>: Select the pooling mode; `add` defaults to `transaction`.
  • --max-client-conn <integer>: Maximum client connections PgBouncer accepts; must be at least 1.
  • --default-pool-size <integer>: Default pool size per user/database pair; must be at least 1.
  • --max-prepared-statements <integer>: Maximum prepared statements per connection; 0 disables it, and it is ignored outside transaction mode.
  • configure setting group (required): At least one of `--pool-mode`, `--max-client-conn`, `--default-pool-size`, or `--max-prepared-statements` is required; multiple may be supplied together.
  • --replicas <integer> (required): Target replica count for `scale`; must be 0 or greater. Documented scaling selects one active region; zero or multiple active regions require direct `railway scale` instead.
  • --yes, -y: Skip the confirmation prompt for add or remove.
  • --no-deploy: Commit the config change without triggering deploys; it applies on the next deploy.
  • Replica count is summed from deploy.multiRegionConfig because production does not write the legacy flat field.
  • Configuration misconfiguration warnings are advisory and never blocking.

FIRST-PARTY EVIDENCE

Check the installed version and the source before using it. Entry JSON

Report a problem with this card