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
  • In AWS, it lives on db-admin

The content-performance-manager, mapit, and transition apps use their own database servers, and do not connect through pgbouncer.

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