Version Support Policy

Which PostgreSQL versions ScalixNova offers, how long each is supported, and how upgrades and end-of-life work

Supported versions

ScalixNova offers these PostgreSQL major versions at database creation:

You pick the major version when you create a database (pg_version in the API, or the selector in the console). It is fixed for the life of the database — branches and point-in-time restores always run the same major as the database they came from.

The policy

• New majors are offered within roughly 90 days of the community GA release, once the extension set (pgvector, PostGIS, pg_trgm, uuid-ossp) is validated on it.
• Each major is supported until its community end-of-life (the PostgreSQL project supports every major for five years).
• At end-of-life: creating new databases on that major is disabled first; existing databases get a six-month migration window with advance notice before the version is retired.
• The default version trails the newest offering deliberately — new databases default to a major that has had time to mature in production. Default changes are announced at least 60 days ahead and never affect existing databases.

Minor versions

Minor releases (security and bug fixes — e.g. 16.14 → 16.15) are managed by Scalix and applied automatically as part of platform updates. No action is needed and no API surface changes; your database's major version never changes without you asking for it.

Moving between majors

In-place major upgrades aren't offered yet. To move a database from one major to another, create a new database on the target version and migrate with pg_dump/pg_restore or logical replication. A managed near-zero-downtime upgrade path (blue/green cutover built on branching) is on the roadmap.