Charmed PostgreSQL K8s
- Canonical
- Databases
Channel | Revision | Published | Runs on |
---|---|---|---|
latest/stable | 20 | 20 Sep 2022 | |
14/stable | 445 | 12 Nov 2024 | |
14/stable | 444 | 12 Nov 2024 | |
14/candidate | 382 | 09 Sep 2024 | |
14/candidate | 381 | 09 Sep 2024 | |
14/beta | 453 | 14 Nov 2024 | |
14/beta | 452 | 14 Nov 2024 | |
14/edge | 460 | Yesterday | |
14/edge | 459 | Yesterday |
juju deploy postgresql-k8s --channel 14/stable
Deploy Kubernetes operators easily with Juju, the Universal Operator Lifecycle Manager. Need a Kubernetes cluster? Install MicroK8s to create a full CNCF-certified Kubernetes system in under 60 seconds.
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.