For new installations, always use the latest stable release. For existing deployments, stay on your current major version and apply minor updates promptly.
Quick recommendation
Which version should I install?
If you are starting fresh on Windows today, install PostgreSQL 18. It is the latest stable release with the longest support horizon (until November 2029) and the newest features. PostgreSQL 16 and 17 are still fully supported but will reach end-of-life sooner.
New installation → PostgreSQL 18. Existing deployment on 16/17 → stay on your version, plan upgrade within the next 1-2 years.
Version comparison
PostgreSQL 16 vs 17 vs 18 on Windows
| Feature / aspect | PG 16 | PG 17 | PG 18 |
|---|---|---|---|
| Release date | Sept 2023 | Oct 2024 | May 2026 |
| End of life | Nov 2028 | Nov 2029 | Nov 2030 |
| Status | Supported | Supported | Latest |
| Logical replication | Improved | Enhanced | Full bidirectional |
| JSON support | Good | Better | Excellent |
| Parallel query | Good | Improved | Further improved |
| Vacuum improvements | Standard | Enhanced | Significant |
| Windows installer | EDB 16.x | EDB 17.x | EDB 18.x |
| pgAdmin bundled | 4.x | 4.x | 4.x |
PostgreSQL 18 highlights
What is new in PostgreSQL 18?
- Asynchronous I/O — significantly improved I/O throughput, especially on Windows with its different I/O model
- Virtual generated columns — computed columns that do not require storage
- OAuth authentication — native OAuth 2.0 support for client authentication
- Improved JSON — more JSON functions and better performance
- pg_basebackup improvements — faster and more reliable physical backups
- Vacuum optimisations — reduced table bloat and faster autovacuum
PostgreSQL 17 highlights
What is new in PostgreSQL 17?
- MERGE improvements — RETURNING clause support and WHEN NOT MATCHED BY SOURCE
- Incremental backup — pg_basebackup now supports incremental backups
- Faster vacuum — up to 20x faster on tables with many dead tuples
- JSON_TABLE — SQL/JSON table function for converting JSON to rows
- COPY improvements — COPY FROM now supports ON_ERROR IGNORE
End of life schedule
Support timeline for Windows
| Version | Released | End of Life | Action needed |
|---|---|---|---|
| 18 | May 2026 | Nov 2030 | Recommended for new installs |
| 17 | Oct 2024 | Nov 2029 | Continue using, plan upgrade to 18 by 2029 |
| 16 | Sept 2023 | Nov 2028 | Continue using, plan upgrade |
| 15 | Oct 2022 | Nov 2027 | Plan upgrade soon |
| 14 | Sept 2021 | Nov 2026 | Upgrade urgently — EOL this year |
| 13 and older | — | Already EOL | Upgrade immediately |
FAQ
Version questions
Can I run PostgreSQL 16 and 18 on the same Windows machine?
Yes. Each major version installs to its own directory and uses a different port by default (the installer assigns 5432 to the first install, then 5433 for the second, etc.). Both services can run simultaneously.
Is upgrading from 16 to 18 safe?
Yes, with preparation. Back up all databases first with pg_dumpall. Then either use the dump/restore method or pg_upgrade. Never skip the backup step. See Upgrade guide.
Do minor versions (16.1, 16.2, etc.) require data migration?
No. Minor version upgrades (e.g. 17.3 to 17.4) are safe to apply by simply running the new installer over the existing one. The data directory and format do not change between minor versions.