PostgreSQL FAQ

The latest stable version of PostgreSQL is 18.3. There are currently 5 actively supported versions and 24 versions that have reached end of life. Visit the PostgreSQL Version Tracker on ReleaseRun for a complete breakdown of all versions, including release dates, support timelines, and end-of-life dates.

PostgreSQL major versions receive 5 years of support from their initial release. During this period, the community releases quarterly minor updates with bug fixes and security patches. After 5 years, the version reaches end of life and receives no further updates.

There are two main approaches: pg_upgrade (in-place, faster, minimal downtime) and pg_dump/pg_restore (logical, safer, requires more disk space and time). For most deployments, pg_upgrade is preferred. Always test the upgrade on a copy of your production database first. Check for deprecated features, extension compatibility, and run ANALYZE after upgrading.

Yes, unlike Kubernetes, you can skip PostgreSQL major versions. pg_upgrade supports upgrading from any supported version to any newer version directly (e.g., 14 to 17). However, review the release notes for every skipped version to understand cumulative breaking changes, removed features, and required configuration updates.

Major versions (14, 15, 16, 17, 18) add new features and may include breaking changes. Minor versions (16.1, 16.2, 16.3) contain only bug fixes and security patches with no new features or breaking changes. Always stay on the latest minor version of your major release.

Wait for the first or second minor release (e.g., 18.1 or 18.2) before deploying a new major version to production. This lets early adopters discover edge-case bugs. Meanwhile, ensure your extensions are compatible with the new version. For critical production systems, the N-1 version is a safe and well-tested choice.