Charmed PostgreSQL K8s

Channel Revision Published Runs on
latest/stable 20 20 Sep 2022
Ubuntu 20.04
14/stable 445 Yesterday
Ubuntu 22.04
14/stable 444 Yesterday
Ubuntu 22.04
14/candidate 382 09 Sep 2024
Ubuntu 22.04
14/candidate 381 09 Sep 2024
Ubuntu 22.04
14/beta 449 Yesterday
Ubuntu 22.04
14/beta 448 Yesterday
Ubuntu 22.04
14/edge 451 Yesterday
Ubuntu 22.04
14/edge 450 Yesterday
Ubuntu 22.04
juju deploy postgresql-k8s --channel 14/edge
Show information

Platform:

Connection pooling

Connection pooling is a strategy to reduce the amount of active connections and the costs of reopening connections. It requires maintaining a set of persistently opened connections, called a pool, that can be reused by clients.

Since PostgreSQL K8s spawns separate processes for client connections, it can be beneficial in some use cases to maintain a client side connection pool rather than increase the database connection limits and resource consumption.

A way to achieve this with Charmed PostgreSQL K8s is by integrating with the PgBouncer K8s charm.

Increasing maximum allowed connections

If using PgBouncer is not enough to handle the connections load of your application, you can increase the amount of connections that PostgreSQL can open via the experimental_max_connections config parameter.

Disclaimer: Each connection opened by PostgreSQL spawns a new process, which is resource-intensive. Use this option as a last resort.

Contact us for more guidance about your use-case.