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/stable
Deploy universal operators easily with Juju, the Universal Operator Lifecycle Manager.
Platform:
22.04
20.04
18.04
16.04
Major Rollback
Example: PgBouncer 2 -> PgBouncer 1
Currently, the charm supports PgBouncer major version 1 only; therefore, minor rollbacks are only possible. Canonical is NOT planning to support in-place rollbacks for the major PgBouncer version change as the old PostgreSQL cluster with the old PgBouncer installation will stay nearby and can be reused for the rollback.