Every Neon project is tied to a specific Postgres major version that you picked at project creation. To check which one you're on, run SELECT version(); from any SQL client, or read it from the Settings widget on the Project Dashboard in the Neon Console. The CLI command neon projects get shows the same value. Neon supports Postgres 14, 15, 16, 17, and 18. See Upgrading your Postgres version for details.
Three ways to check
Run this from the Neon SQL Editor, psql, or any Postgres client:
SELECT version();You'll get a string like:
PostgreSQL 17.2 on x86_64-pc-linux-gnu, compiled by gcc ...The first number is the major version. The second is the minor version, which Neon upgrades automatically.
Major vs minor versions
Neon manages minor version upgrades for you under the Postgres version support policy. Minor versions are deployed soon after release and typically don't require any action on your part.
Major versions (16 to 17, 17 to 18, and so on) are not upgraded automatically because they can introduce incompatibilities. You upgrade by creating a new Neon project with the target major version and migrating your data with the Import Data Assistant, pg_dump / pg_restore, or logical replication.
Major versions cannot be downgraded
Once a Neon project is created with a given major version, you cannot move it backward. You also can't change the major version on an existing project. To run a different major version, create a new project and migrate. Pick carefully if you have strict compatibility requirements.
Walk through creating a new project, migrating data, and cutting traffic over to the new version.