Skip to main content
Table of contents



PgBouncer sits between our apps and PostgreSQL. It performs connection pooling, and can also treat databases on remote hosts as if they were local. From the perspective of an app, it is talking to a regular PostgreSQL server.

Where it lives

  • In Carrenza, it lives on postgresql-primary-1.backend
  • We do not use pgbouncer in AWS

The content-data-api, mapit, and transition apps use their own database servers, and do not connect through PgBouncer.

This page was last reviewed on 21 October 2019. It needs to be reviewed again on 21 January 2020 by the page owner #govuk-2ndline .
This page was set to be reviewed before 21 January 2020 by the page owner #govuk-2ndline. This might mean the content is out of date.