Versions and lifecycle
Numspot operates its PostgreSQL clusters with stable versions that benefit from active security patch tracking, in compliance with the security requirements applied to the service.
Supported versions
The following major versions are supported:
- PostgreSQL 16
- PostgreSQL 17
- PostgreSQL 18
This scope covers the stable versions that are actively maintained by the PostgreSQL community, with continuous tracking of security advisories.
When you create a cluster, the most recent version is selected by default. For more information, see Create a PostgreSQL cluster.
Security patch tracking
The images used for the PostgreSQL clusters are based on TimescaleDB HA images and include:
- minor (patch) updates applied regularly to fix bugs and security vulnerabilities;
- active tracking of critical and high-severity vulnerabilities.
Minor updates are applied automatically by Numspot and require no action from the customer. They only concern patch versions (for example, 17.2 to 17.5), without any change to data compatibility.
To obtain information about the applied versions or recent patches, contact Numspot support.
Version lifecycle
Support policy
| Version | Support status | Community end-of-support date | Estimated Numspot end-of-support |
|---|---|---|---|
| 16 | Active | November 2028 | November 2028 |
| 17 | Active | November 2029 | November 2029 |
| 18 | Active | November 2030 | November 2030 |
The support status is aligned with the dates announced by the PostgreSQL project. Numspot follows the PostgreSQL policy regarding the support of major versions.
End-of-support notification
Numspot notifies its customers several months before the end of support of a major version. This notification allows customers to plan the migration to a more recent version.
Major updates
Major updates (for example, from PostgreSQL 17 to PostgreSQL 18) require the creation of a new cluster. Numspot recommends testing the compatibility of your applications before performing a major update.
Numspot cannot guarantee backward compatibility between major versions. It is the customer's responsibility to verify that their applications are compatible with the new version before any migration.