Support for Postgres 17
We're excited to announce that Neon now supports Postgres 17. To start using Postgres 17, create a new Neon project and select 17 as the Postgres version. For detailed instructions, refer to our Create a project guide.
If you need to migrate data from an existing Neon project to one running Postgres 17, check out our Upgrading your Postgres version guide for supported migration options.
As always, it's important to thoroughly test before migrating production data or applications. We recommend reviewing the key changes in Postgres 17, which you can find in the Postgres Release 17 documentation.
Early Access to AI Features in Neon SQL Editor
Join our Early Access Program to try out the AI features we're testing in the Neon SQL Editor.
Explore three AI-driven features:
- SQL generation: Convert natural language requests to SQL with ease. Press the ✨ button or use Cmd/Ctrl+Shift+M, type your request, and the AI assistant will generate the corresponding SQL. It’s schema-aware, so you can reference table names, functions, and other objects in your schema.
- Fix with AI: When your query returns an error, click Fix with AI next to the error message. The AI assistant will analyze the issue, suggest a fix, and update the SQL Editor so you can run the query again.
- AI-generated query names: Queries in the Neon SQL Editor's History are automatically assigned descriptive names. This feature helps you quickly identify and reuse previous queries.
A new Postgres toolkit for AI agents and test environments
We're excited to announce an experimental release of the @neondatabase/toolkit (@neon/toolkit on JSR). This toolkit lets you spin up a Postgres database in seconds and run SQL queries. It includes both the Neon API Client and the Neon Serverless Driver, making it an excellent choice for AI agents that need to quickly set up an SQL database, or for test environments where manually deploying a new database isn't practical.
With a few lines of code, you can create a Postgres database on Neon, run SQL queries, and tear down the database when you're done. Here's a quick look:
As with all of our experimental features, changes are ongoing. If you have any feedback, we'd love to hear it. Let us know via the Feedback form in the Neon Console or our feedback channel on Discord.
Fixes & improvements
-
Released a new version of the Neon CLI with the following updates:
- Fixed an issue where the
neonctl -v
command returnedunknown
instead of the CLI version. - Updated the neon projects create CLI command to support creating projects in the
aws-ap-southeast-2
region, which was missing from the list of supported regions. - Added a warning to the neon branches create CLI command output for branches created from a protected parent branch. The warning notes that role passwords are changed. For more details, see New passwords generated for Postgres roles on child branches.
To update your Neon CLI version, follow our CLI upgrade instructions.
- Fixed an issue where the
-
The Drizzle Studio version that powers the Tables page in the Neon Console has been updated. For improvements and fixes in this version, see the Neon Drizzle Studio Integration Changelog.
-
We removed a restriction that prevented using the Schema Diff feature when IP Allow was enabled. Previously, Schema Diff couldn't compare branches protected by an IP Allow list.
-
Fixed an issue where timestamp values were displayed incorrectly on the Tables page. Timestamps were stored in UTC but shown in the user's local time zone.
-
Improved error messages on the Tables page after a Drizzle Studio connection failure.
-
The Refresh button on the Monitoring page now correctly refreshes any charts displaying an error.
-
Branch deletion operations triggered by a new preview deployment in the Neon Vercel Integration are now performed asynchronously, allowing preview deployment operations to proceed without delay.
-
Improved handling of long names for projects, branches, roles, and databases in the Neon Console.
-
Fixed an issue in the Neon Quickstart where the connection string would disappear and reappear.
-
Fixed an issue with storage usage values not updating correctly at the start of a new billing period after deleting all projects and downgrading.