ubicloud/rhizome/postgres/bin
shikharbhardwaj 615050d2f8 Add Upgrade steps to Prog::Postgres::ConvergePostgresResource
The Converge prog is now also responsible for matching the current
Postgres version to the desired version. If there is a mismatch (current
< desired), the Converge prog is launched.

Roughly, the Converge prog does the following:
1. Provisions new servers. In case of upgrades, it only provisions upto
   one new standby if no existing standby is suitable for
   upgrades.
2. Wait for the required servers to be ready.
3. Wait for the maintenance window to start.
4. Fence the primary server, and launch pg_upgrade.
5. If the upgrade is successful, replace the current primary with the
   candidate standby.

In case the upgrade fails, we delete the candidate standby and unfence the
primary to bring the database back. During the Upgrade health checking
is effectively disabled as the auto-recovery causes conflicts with the
several restarts of various versions on the candidate.
2025-09-24 01:45:32 +02:00
..
configure Propagate user configs to PG server 2025-07-01 17:28:29 +05:30
configure-hugepages Configure hugepages for Postgres 2025-06-30 17:16:50 +05:30
initialize-database-from-backup Make PG run with unified image 2025-09-23 20:59:30 +02:00
initialize-empty-database Make PG run with unified image 2025-09-23 20:59:30 +02:00
install-wal-g Implement backup taking for PostgreSQL servers 2023-11-14 17:06:11 +01:00
lockout Don't close ubi_replication's connections 2025-07-07 19:11:45 +03:00
promote Add Upgrade steps to Prog::Postgres::ConvergePostgresResource 2025-09-24 01:45:32 +02:00
restart Update data plane Postgres scripts to accept version as parameter 2024-10-25 13:44:27 +03:00
setup-hugepages Avoid hugepage allocation when PG is running 2025-07-01 16:30:19 +05:30
take-backup Update data plane Postgres scripts to accept version as parameter 2024-10-25 13:44:27 +03:00
upgrade Add rhizome changes for Postgres Major version upgrades 2025-09-23 21:07:30 +02:00