The database version the application was written against
PostgreSQL drops a major version off community support every year. A major upgrade means a dump/restore or logical replication cutover -- planned downtime for a database that usually can't have any.
Challenge
PostgreSQL major upgrades are not in-place. Either a dump and restore, which scales with data size, or a logical replication cutover, which is its own project. Both need a maintenance window the business has to agree to.
Environment
PostgreSQL 12, 13 or 14 carrying production data, past or approaching community end of life.
Approach
OSSeva patches the running major version so the upgrade stops being a security deadline, and designs the cutover -- dump/restore or logical replication -- against the actual data volume and downtime budget.
What this delivers
A patched database on the current major version, and a major upgrade scheduled on the business's terms.