PgBouncer
- Canonical
- Databases
Channel | Revision | Published | Runs on |
---|---|---|---|
latest/stable | 5 | 17 Jan 2022 | |
1/stable | 397 | 11 Sep 2024 | |
1/stable | 396 | 11 Sep 2024 | |
1/stable | 395 | 11 Sep 2024 | |
1/stable | 394 | 11 Sep 2024 | |
1/candidate | 397 | 02 Sep 2024 | |
1/candidate | 396 | 02 Sep 2024 | |
1/candidate | 395 | 02 Sep 2024 | |
1/candidate | 394 | 02 Sep 2024 | |
1/beta | 397 | 29 Aug 2024 | |
1/beta | 396 | 29 Aug 2024 | |
1/beta | 395 | 29 Aug 2024 | |
1/beta | 394 | 29 Aug 2024 | |
1/edge | 530 | Yesterday | |
1/edge | 529 | Yesterday | |
1/edge | 528 | Yesterday | |
1/edge | 527 | Yesterday |
juju deploy pgbouncer --channel 1/edge
Deploy universal operators easily with Juju, the Universal Operator Lifecycle Manager.
Platform:
Release Notes
This page provides high-level overviews of the dependencies and features that are supported by each revision in every stable release. To learn more about the different release tracks, see the Juju documentation about risk levels.
To see all releases and commits, check the Charmed PgBouncer Releases page on GitHub.
Dependencies and supported features
For each release, this table shows:
- The PgBouncer version packaged inside
- The minimum Juju version required to reliably operate all features of the release
This charm still supports older versions of Juju 2.9. See the system requirements for more details
- Support for specific features
Release | PgBouncer version | Juju version | TLS encryption | COS monitoring | Minor version upgrades |
---|---|---|---|---|---|
394, 395, 396, 397 | 1.21.0 |
3.4.5+ |
|||
278, 279, 280, 281 | 1.21.0 |
3.4.5+ |
|||
254, 255, 256, 257 | 1.21.0 |
3.1.8+ |
|||
173, 174, 175, 176 | 1.21.0 |
3.1.8+ |
|||
88, 89 | 1.21.0 |
3.1.7+ |
|||
80, 81 | 1.21.0 |
3.1.6+ |
|||
76, 77 | 1.18.0 |
3.1.6+ |
Architecture and base
Due to the subordinate nature of this charm, several revisions are released simultaneously for different bases/series using the same charm code. In other words, one release contains multiple revisions.
If you do not specify a revision on deploy time, Juju will automatically choose the revision that matches your base and architecture.
If you deploy a specific revision, you must make sure it matches your base and architecture via the tables below or with
juju info
.
Release 394-397 (1/stable
)
Our release notes are an ongoing work in progress. If there is any additional information about releases that you would like to see or suggestions for other improvements, don’t hesitate to contact us on Matrix or leave a comment.