Changelog

We're now in Australia

Neon is now available in the Asia Pacific (Sydney) region.

You can select the region for your Neon project during project creation. See Create a project.

For information about the regions Neon supports, see Regions.

Postgres extension update for plv8

We updated the plv8 extension to version 3.1.10. If you installed this extension previously and want to upgrade to the latest version, please refer to Update an extension version for instructions.

plv8 is a Javascript language extension for Postgres. To learn more, refer to the PLV8 documentation. For a list of all Postgres extensions supported by Neon, see Supported Postgres extensions.

Vercel integration enhancements

The following updates were made to the Neon Vercel Integration:

• Preview deployment branches are now created from the primary branch of your Neon project. Previously, the integration created branches from the root branch of your Neon project, which is designated as your project's primary branch by default. Neon lets you change your primary branch. If you have an older version of the integration and you want branches created from your project's primary branch instead of root, reinstall the integration from the Vercel Marketplace.
• The integration now appends the sslmode=require option to the Neon connection string that it sets for the DATABASE_URL environment variable in Vercel.
• Fixed an issue that prevented using the integration with more than one Vercel project.
• Fixed an issue that set the DATABASE_URL variable in the Vercel project settings to a pooled Neon database connection string instead of a direct database connection string.

Fixes & improvements

• Free Tier users with access to a project shared by a Neon Pro Plan account can now submit support requests via the Support link in the Neon Console sidebar.
• Fixed an issue that caused shared projects to be displayed under Projects instead of Shared with me on the Projects page in the Neon Console.
• The Edit compute modal, accessed via the Branches page in the Neon Console, was reimplemented as a side drawer.

What's new in docs?

To help our users unlock the full potential of Postgres, we're building out our Postgres function documentation. Whether you're a seasoned Postgres user or new to the platform, our new function guides can help you get started.

• array_to_json()
• dense_rank()
• json_array_elements()
• jsonb_array_elements()
• json_build_object()
• json_each()
• json_extract_path()
• json_extract_path_text()
• json_object()
• json_populate_record()
• json_to_record()

Postman public workspace and collection for the Neon API

We've published a Postman public workspace and collection for the Neon API:

• Neon API Workspace
• Neon API Collection

From the Neon blog

In case you missed them, be sure to check out our latest blog posts:

• Support Case Recap: Resolving connection limit errors
• Bring your own S3 to Neon
• Using Python & Django with Neon Serverless Postgres
• Why Topo.io Switched From Amazon RDS to Neon

New default Postgres version

The default version for newly created Neon projects is now Postgres 16. Neon continues to support Postgres 14 and 15.

Configurable environment variables for Vercel Integration

• The Neon Vercel Integration is now supported with applications sourced in GitLab and Bitbucket. Previously, the integration only worked with applications stored in GitHub.

• The environment variables set by the Neon Vercel Integration when you add the integration to a Vercel project have changed. Previously, the integration set the following Postgres variables:

  • DATABASE_URL
  • PGHOST
  • PGUSER
  • PGDATABASE
  • PGPASSWORD

  The integration now sets only the DATABASE_URL variable by default, which includes all of the required details for connecting to your Neon database.

  If you prefer to use the other Postgres variables with your application instead of DATABASE_URL, you can now configure the variables you want on the Integrations page in the Neon console.

  

  The variables you select are set in your Vercel project on your next git push. For details, see Manage Vercel environment variables.

• Fixed an issue that prevented the DATABASE_URL variable from being set on the first preview deployment after adding the integration to a Vercel project.

Fixes & improvements

• The List projects API method now returns only projects owned by the current user account. Previously, it also returned projects shared with the current user account. To list projects shared with the current user account, use the List shared projects API method instead.
• Added a Submit feedback form to the cards on the Integrations page in the Neon Console, letting users share their experience with Neon integrations.
• We now expose more details in error messages returned from the Neon proxy for Neon serverless driver connections over HTTP.
• Improved the IP Allow user interface with minor design and copy adjustments.

What's new in docs?

To help our users unlock the full potential of Postgres, we're building out our Postgres extension documentation. Whether you're a seasoned Postgres user or new to the platform, our new extension guides can help you get started.

• The pg_stat_statements extension
• The timescaledb extension
• The postgis extension
• The hstore extension
• The citext extension
• The pg_trgm extension

See our updated roadmap to learn about upcoming features and share your ideas:

• Neon roadmap

Success stories

We are excited to announce the launch of our Success Stories page on the Neon website. This new page highlights real-world experiences and success stories from our valued partners and customers.

From the Neon Blog

In case you missed them, be sure to check out our latest blog posts:

• See you at FOSDEM and FOSDEM PGDay 2024
• Using Neon’s Auto-Suspend with Long-Running Applications

Custom extension support

Neon supports custom-built Postgres extensions for exclusive use with your Neon account. If you developed your own Postgres extension and want to use it with Neon, you can reach out to our Support team. To learn more about how we support custom extensions, check out this blog post: Bring Your Own Extensions to Serverless PostgreSQL.

Neon API updates

• Added API methods for Neon's project sharing feature. The new methods allow you to:
  • List users that a project is shared with. See Return project permissions.
  • Share a project with a specified user. See Grant project permissions.
  • Revoke project access from a user you shared a project with. See Revoke project permissions.
• Neon API methods such as Get projects, which return the creation source in the response body, now return "creation_source": "vercel" for projects and branches created by the Neon Vercel Integration.
• The ips field in the allowed_ips object in the Create project and Update project APIs was changed from required to optional. This change allows certain IP Allow requests to be sent from the interactive Neon API reference without specifying IP addresses.

Neon CLI updates

The Neon CLI now includes an ip-allow command, which supports list, add, remove, and reset actions on the IP allowlist for your Neon project. For details, see Neon CLI commands — ip-allow. To install the Neon CLI or update your installation to the latest version, see Neon CLI — Install and connect.

Fixes & improvements

• Added several new integration cards to the Request section of the Integrations page in the Neon Console where you can express your interest and share your feedback about future integrations with Neon. Your input helps the Neon team design and prioritize integrations. To learn how to participate, see Express interest in upcoming integrations.
• Added a dialog requiring user confirmation when removing all IP addresses from an IP Allow configuration.
• The Community link in the Neon Console sidebar has been updated to direct users to the Neon Discord server, rather than the Neon Discourse forum.
• To prevent connection errors at the subscriber and repeated compute restarts, Neon no longer autosuspends a compute instance with an active connection from a logical replication susbscriber.
• To allow Postgres autovacuum operations to complete their work without interruption, Neon no longer suspends a compute due to inactivity while an autovacuum operation is in progress.
• Fixed an issue in Neon Console confirmation dialogs that caused an "Unknown error".
• Fixed an issue preventing the Connection Details widget from displaying code snippets when accessing the Neon Console from a mobile device.
• Fixed a UI text consistency issue on the Role Created modal that is displayed after creating a new role in the Neon Console.

Neon application demos

Check out our new Demos page showcasing Neon Serverless Postgres application examples.

What's new in docs?

We have a couple of new guides for you to check out this week:

• Add MongoDB compatibility to your Neon database with FerretDB
• Connect a Ruby on Rails application to Neon Postgres

Customer case study

Read about how Branch chose Neon for its true Postgres and serverless nature.

From the Neon Blog

In case you missed them, be sure to check out our latest posts:

• Moving scale-to-zero workloads from Aurora Serverless V1 to Neon
• How to build AI-powered apps using Postgres and DronaHQ

Fixes & improvements

• The Neon CLI now supports get operations for branches with numeric names. Previously, only string values were supported.
• Corrected the Neon CLI package name that appears in Quickstart banner on the Neon Dashboard. The package name shown in the Windows and Linux installation commands was incorrect.
• The neon_superuser role is now able to execute the pg_stat_statements_reset() function that is part of the pg_stat_statements extension. This function discards statistics gathered so far by pg_stat_statements. Roles created in the Neon console, CLI, or API, including the default role created with each Neon project, are granted membership in the neon_superuser role. Previously, this function could only be run with a Postgres superuser role, which is restricted in Neon. To make this enhancement available, drop and recreate the pg_stat_statements extension. See Install an extension.
• For logical replication, the PostgreSQL max_slot_wal_keep_size is now set to 1 GB, limiting the maximum size of WAL files that replication slots are allowed to retain in the pg_wal directory. This is a temporary limit that will be removed in a future release. The limit avoids an accumulation of WAL data at the publisher due to a lagging subscriber, which could cause a slow compute start.
• Added a Vercel integration card to the Integrations page in the Neon Console.
• Fixed the Cancel action in card drawers on the Integrations page in the Neon Console. When clicking Cancel, card drawers did not close.

To follow Neon storage and compute releases in GitHub, see Releases.

What's new in docs?

• Check out our new guide that describes how to replicate data from Neon with Fivetran.
• Want to better understand how Neon's project billing works? We've added a real-world example of a generative AI project with 80,000 daily active users that walks you through estimating a monthly bill. See Sample billing.
• Find a typo in the Neon docs? Is there a section that's hard to understand? Notice that a certain topic is missing? The Neon docs are open-source, and contributions are welcome. See our Documentation Contribution Guide for details.

From the Neon Blog

In case you missed them, be sure to check out our latest posts.

• Logical Replication and CDC in PostgreSQL with Airbyte

  Learn how to synchronize your PostgreSQL and Airbyte data in this community-contributed blog post by Jacob Prall, Senior Developer Advocate at @Airbyte:

  A Guide to Logical Replication and CDC in PostgreSQL with Airbyte

• Publish a custom ChatGPT

  Learn how to create and publish a custom ChatGPT with this post from Peter Bendel, Postgres Performance Engineer @Neon, and Raouf Chebri Developer Advocate @Neon:

  OpenAI’s GPT Store is live: Create and Publish a custom Postgres GPT Expert

Control access to your data with IP Allow

Neon's IP Allow feature, now available with the Neon Pro Plan, ensures that only trusted IP addresses can connect to the project where your database resides, preventing unauthorized access and helping maintain overall data security. You can limit access to individual IP addresses, IP ranges, or IP addresses and ranges defined with CIDR notation.

To get started, see Configure IP Allow.

Change Data Capture (CDC) with Logical Replication

Neon is pleased to announce support for logical replication, which brings Change Data Capture (CDC) to serverless Postgres. You can now stream data from your Neon database to a variety of external destinations, including data warehouses, analytical database services, messaging platforms, event-streaming platforms, and external Postgres databases. Logical replication is available to all Neon users.

To get started, jump into one of our step-by-step logical replication guides:

• Replicate data with Airbyte
• Replicate data with Kafka (Confluent) and Debezium
• Replicate data to Materialize
• Replicate data to an external Postgres instance

Also, check out these blog posts from Neon and Materialize:

• Change Data Capture with Serverless Postgres
• Change Data Capture with Neon and Materialize

Postgres version update

Supported Postgres versions were updated to 14.10, 15.5, and 16.1, respectively.

Fixes & improvements

• Added the REPLICATION privilege to the neon_superuser role. The REPLICATION privilege was introduced with the release of logical replication support in Neon. Only the default Postgres role created with your Neon project and roles created using the Neon Console, CLI, or API are granted membership in the neon_superuser role, which includes the REPLICATION privilege. Granting the REPLICATION privilege to roles created via SQL is currently not permitted.
• Added support for browser-issued SQL-over-HTTP batch queries using the Neon serverless driver. Batch queries were failing because Neon-Batch-Isolation-Level and Neon-Batch-Read-Only headers were missing from the server's OPTIONS response.

Quickstart

We've revised the Quickstart panel that appears at the top of the Neon project Dashboard after creating a new project. Follow this Quickstart to learn about passwordless authentication, installing the Neon CLI, integrating your apps with Neon, and importing data into your project.

Fixes & improvements

• Fixed the Create Support Ticket form that is accessed from the Support link in the Neon Console sidebar. The form was not functioning properly.
• Fixed the Cancel link in the drawer that opens when you request an integration on the Integrations page in the Neon Console. Clicking Cancel now closes the drawer, as expected.

Branch reset

Neon is pleased to announce the latest branching feature to help improve your development workflows: branch reset.

With one click, you can now update your working branch to the latest available schema and data from its parent branch, avoiding labor-intensive and error-prone manual updates or branch restorations. This action is available from both the Neon Console and the Neon CLI. For details, see Reset branch from parent.

Set context for the Neon CLI

Using a new neonctl command, set-context, you can now set a background context for your CLI sessions, letting you perform project or branch-specific actions without having to specify the project or branch id in every command. See Neon CLI commands — set-context for more detail.

Support for timescaledb 2.13.0 for Postgres 16

The timescaledb extension, version 2.13.0, which enables scalable inserts and complex queries for time-series data, is now available on Postgres 16.

For a complete list of Postgres extensions supported by Neon, see Postgres extensions.

Fixes & improvements

• UI: Fixed an unresponsive Read-only (RO) radio button option that appears on the Create Compute Endpoint modal.

Integrations page in Console

The Integrations page in the Neon Console provides a hub for managing third-party integrations with your Neon project.

When visiting the Integrations page, you'll notice different categories:

• Available: These are integrations available for you to add and use immediately.
• Coming soon: These are the integrations that will be available in the near future.
• Request an integration: An option for you to request new integrations.

We've recently added several integrations to our Coming soon category. You can express your interest in a particular integration by clicking Request and sharing your use case, which helps us prioritize and build for exactly what you need. Have a look and let us know what integration you would like Neon to build next.

Fixes & improvements

• Proxy: Enabled channel binding in the Neon proxy, which is an additional security measure that ties the authentication process (using SCRAM) to the specific secure communication channel, protecting it from advanced types of cyberattacks where the attacker is able to intercept and mimic secure communication channels.

Fixes & improvements

• API: An operation was added to the Update project API response. An apply_storage_config operation is now returned when updating the history_retention_seconds value. If your application uses this API to modify the history_retention_seconds value and expects a specific response, you may need to make code adjustments.

  Read more about operations here: Operations.