Postgres Roadmap 2026: Learn, Pick a Version, Upgrade
10 min read ยท 2026-10-31
A good postgres roadmap takes you from your first query to running a production database in about six months. You learn in this order: SQL and psql, schema design, indexes and query plans, transactions and MVCC, security and operations, then replication and version upgrades. Each phase builds on the one before and ends with a milestone you can check.
The PostgreSQL project does not publish a roadmap of upcoming features. It does publish a release schedule, and anyone who owns a Postgres database has to follow it. So this guide gives you two things: the learning plan, and the 2026 version calendar. The calendar tells you which release to learn on, which one to run in production and when to upgrade.
The roadmap at a glance
Goal: Learn PostgreSQL well enough to design, tune, secure, upgrade and operate databases for real applications. Duration: 6 months
SQL and psql (Weeks 1 to 4)
Get fluent with SQL and the native Postgres tools.
- Run PostgreSQL 18 locally with Docker or Postgres.app and connect with psql.
- Learn the psql meta-commands for listing tables, describing objects and timing queries.
- Write SELECT queries with filters, joins, GROUP BY and HAVING on the Pagila sample database.
- Use CTEs, subqueries and window functions to answer analytical questions.
- Write INSERT, UPDATE, DELETE and INSERT ON CONFLICT upserts safely.
Milestone: Answer thirty analytical questions on a sample database using only psql.
Schema and Types (Weeks 5 to 8)
Design schemas that use Postgres features to keep data correct.
- Choose the right types, such as text, numeric, timestamptz, uuid and enums.
- Use identity columns, foreign keys, CHECK constraints and exclusion constraints.
- Store semi-structured data in JSONB and query it with its operators and functions.
- Manage schema changes with a migration tool like Flyway, Sqitch or your framework's migrations.
Milestone: A normalized schema for a multi-tenant SaaS app, with every migration stored in Git.
Indexes and Query Plans (Weeks 9 to 12)
Understand how Postgres runs a query and make it fast.
- Read EXPLAIN ANALYZE output: scan types, join types and row estimates.
- Create B-tree, composite, partial and expression indexes for real query patterns.
- Use GIN indexes for JSONB and full-text search, and GiST for ranges and geometry.
- Find slow queries with the pg_stat_statements extension.
Milestone: Load a dataset of several million rows and speed up five slow queries, with before and after plans.
Transactions and Concurrency (Weeks 13 to 16)
Write correct code under concurrent load.
- Learn how MVCC creates row versions and why VACUUM and autovacuum exist.
- Compare Read Committed, Repeatable Read and Serializable with your own experiments.
- Use SELECT FOR UPDATE, SKIP LOCKED and advisory locks to build a job queue.
- Reproduce a deadlock between two sessions, then fix it.
Milestone: A job queue table that several workers process without duplicates.
Security and Operations (Weeks 17 to 21)
Run Postgres safely, with access control and a tested recovery plan.
- Create least privilege roles and configure pg_hba.conf with SCRAM-SHA-256 passwords.
- Add row-level security policies for tenant isolation.
- Back up with pg_dump, then restore with pg_restore into a fresh instance.
- Set up point-in-time recovery with WAL archiving using pgBackRest or WAL-G.
- Tune shared_buffers, work_mem and connection limits, and add PgBouncer.
Milestone: Restore a database to a chosen point in time from your own backups.
Replication and Upgrades (Weeks 22 to 26)
Handle growth and move between major versions without losing data.
- Configure streaming replication with a read replica and test failover.
- Partition a large time-series table by range and measure the effect.
- Upgrade a test database from PostgreSQL 14 to 18 with pg_upgrade, then repeat it with logical replication.
- Monitor with the pg_stat views and a dashboard such as Grafana with postgres_exporter.
- Write runbooks for backup, restore, failover and upgrade.
Milestone: A replicated, monitored, backed-up database that you have upgraded one major version, with written runbooks.
Is There an Official PostgreSQL Roadmap?
No. The project's Roadmap page, read on October 30, 2026, describes PostgreSQL as "a noncommercial, all volunteer, free software project", so there is no formal list of features required for a release. Contributors choose what they work on, and the community reviews every new feature before it gets in. When people search for a PostgreSQL roadmap, they usually want one of three things: the release calendar, a way to follow upcoming features, or a learning path. This guide covers all three.
The release calendar is the part you can plan around. The same Roadmap page says the project aims to ship at least one minor release every quarter, on a set schedule. The next dates listed are November 12, 2026, February 11, 2027, May 13, 2027 and August 12, 2027.
For the next major version, PostgreSQL 19 Release Candidate 1 came out on October 15, 2026. PostgreSQL 19 is not released yet as of October 30, 2026. The Roadmap page gives October 2026 as the target for the final release, with no exact day. The project's RC announcement says not to run release candidates in production. Check the official news page for the release before you book an upgrade window.
To see what is coming before a release, follow these sources:
- CommitFest: the status of every patch under review in the current cycle.
- Development information wiki: how the development process works, from proposal to commit.
- Developer FAQ: answers for people who want to read or join the work.
- Release notes: the detailed list of changes for each major and minor version.
PostgreSQL Roadmap 2026: Versions and End of Life Dates
Each major version gets about five years of fixes, then support stops. The dates below come from the official Versioning Policy page, read on October 30, 2026.
The current minor releases (14.24, 15.19, 16.15, 17.11 and 18.6) all came out on August 13, 2026. PostgreSQL 19 is not in the list yet because it has not shipped. If you run 14 today, your database stops getting fixes on November 12, 2026. That makes the upgrade phase of this roadmap urgent, not optional.
- PostgreSQL 18: latest minor 18.6, first released September 25, 2025, end of life November 14, 2030.
- PostgreSQL 17: latest minor 17.11, first released September 26, 2024, end of life November 8, 2029.
- PostgreSQL 16: latest minor 16.15, first released September 14, 2023, end of life November 9, 2028.
- PostgreSQL 15: latest minor 15.19, first released October 13, 2022, end of life November 11, 2027.
- PostgreSQL 14: latest minor 14.24, first released September 30, 2021, end of life November 12, 2026.
Which PostgreSQL Version to Use
Pick the version by what you are doing with it, and keep the end of life dates in view.
- Learning and new projects: PostgreSQL 18.
- Existing production on 17: stay there if your application or a vendor has not certified 18 yet. Support runs until November 2029.
- PostgreSQL 19: install the release candidate on a staging server to test your queries and extensions. Move production only after the final release, once your tools support it and the first minor releases are out.
Upgrade Skills Every Postgres Owner Needs
Knowing SQL is not enough to own a database. Sooner or later you will move it to a new major version, and the method you pick decides how long your users wait. There are three main options.
- pg_upgrade: converts the data files in place. In link mode it does not copy the data files, so downtime is much shorter than a dump and restore.
- pg_dump and pg_restore: export, then import into the new version. Downtime grows with the size of the database.
- Logical replication: copy the data to a new server running the new version while the old one keeps working, then make a short switch.
PostgreSQL 18 Changes That Can Break an Upgrade
Some changes in PostgreSQL 18 can break an upgrade if nobody plans for them. The PostgreSQL 18 release notes, read on October 30, 2026, list two that matter most.
Read the release notes of every major version you skip, test on a copy of production, and keep a rollback plan ready before the real switch.
- Data checksums are on by default. initdb now enables them. pg_upgrade needs matching checksum settings on the old and new clusters, so to upgrade an old cluster without checksums, create the new one with the --no-data-checksums option.
- MD5 password authentication is deprecated. CREATE ROLE and ALTER ROLE now warn when you set an MD5 password, and the release notes say support will be removed in a future major version. Move users to SCRAM-SHA-256 now, while old clients still connect.
Prerequisites Before You Start
You need basic comfort with the command line and a general idea of what a database does. SQL experience speeds up the first month but is not required, because the roadmap starts with SQL itself. For the last two phases, some Linux, Docker and configuration editing will save you time.
If you are a developer, keep your application language at hand. Connecting Postgres to a Node, Python, Go or Java app through a proper driver and a connection pool teaches what pure SQL drills miss: parameterized queries, transaction boundaries in code, and why too many connections hurt performance.
What Makes PostgreSQL Different
Postgres is more than a generic SQL database. Its strengths are a rich type system, strong constraints, extensions and a capable query planner. JSONB with GIN indexes lets you mix relational and document data. Range types with exclusion constraints can block double bookings at the database level.
Its concurrency model shapes how you design systems. With MVCC, readers do not block writers, but every update leaves a dead row version that vacuum has to clean up. That explains table bloat, why long transactions are dangerous, and why autovacuum settings matter on busy tables.
Practice Projects for Each Stage
Pick projects that push you into features you would otherwise skip. Use realistic volumes: many performance problems only show up past a few million rows, and generate_series can create that data for you.
Treat at least one project like production. Run it on a small server, set up backups, break things on purpose and recover. Practicing a restore before you need one is the most valuable exercise in this roadmap.
- A booking system that uses range types and exclusion constraints to prevent overlaps.
- A multi-tenant API with row-level security for tenant isolation.
- A full-text search engine over public documents with tsvector and GIN.
- A semantic search prototype with pgvector next to relational filters.
How to Know You Are Ready
You are ready to own a Postgres database when you can design a schema with the right types and constraints, fix a slow query found in pg_stat_statements, explain how MVCC and vacuum interact, restore from backup without a guide, and plan a major version upgrade with a rollback path.
A good test is a mock incident. A table is bloated, a query got slower after a deploy, the database must go back to ten minutes ago, and version 14 reaches end of life next month. If you know which views to check, which commands to run and in what order, you are ready for production.
Common mistakes to avoid
- Using timestamp without time zone for event times causes subtle bugs, so default to timestamptz.
- Adding indexes without reading EXPLAIN wastes space and slows writes, so index from measured query plans.
- Leaving transactions open in application code blocks vacuum, so keep them short and watch idle sessions.
- Trusting backups you have never restored is a gamble, so schedule regular restore drills.
- Running a version past its end of life leaves you without fixes, so plan the upgrade at least one quarter before the date.
- Upgrading to 18 without checking checksum settings makes pg_upgrade fail, so match the settings of the old cluster when you run initdb.
- Keeping MD5 passwords puts you at risk when support is removed, so move every role to SCRAM-SHA-256 before your next major upgrade.
Frequently asked questions
Does PostgreSQL publish a feature roadmap?
No. The project is run by volunteers and has no formal list of features for each release. You can follow upcoming work on the CommitFest site and the development wiki, and the release notes confirm what actually shipped.
When is PostgreSQL 19 released?
It is not released yet as of October 30, 2026. Release Candidate 1 came out on October 15, 2026, and the official Roadmap page gives October 2026 as the target, with no exact day. Check the official PostgreSQL news page for the confirmed release before you plan any upgrade.
Which PostgreSQL version should I learn in 2026?
Learn on PostgreSQL 18. It is the latest stable version, it gets fixes until November 14, 2030, and what you learn carries over to 19. Use 17 only if your workplace or a vendor requires it.
Is a PostgreSQL roadmap 2025 still valid in 2026?
The learning order still holds, since SQL, schema design, indexing, MVCC and operations have not changed. The calendar is what changed: version 14 reaches end of life on November 12, 2026, version 19 is in release candidate, and 18 turns on data checksums by default and deprecates MD5 passwords.
How long does it take to learn PostgreSQL?
Basic queries and schema design take one to two months of regular practice. Indexing, query plans, MVCC, backups, replication and upgrades bring the total to about six months. Real confidence comes from running a database through incidents and at least one major upgrade.