Search faster with pg_search on Neon

pg_search extension

We’ve partnered with ParadeDB to bring pg_search to Neon, delivering up to 1,000x faster full-text search inside Postgres. The pg_search extension introduces Elasticsearch-grade ranking, typo tolerance, faceted search, and JSON-aware filtering—all within Postgres. Powered by a BM25-based inverted index, pg_search outperforms native Postgres FTS (tsvector/tsquery), making it ideal for search-heavy applications. It’s available now for Neon databases running Postgres 17 on AWS. To learn more, read the announcement and check out our pg_search docs.

Neon spend is now MACC-eligible on Azure

Neon Postgres purchases made through the Azure Marketplace are now counted toward your Microsoft Azure Consumption Commitment (MACC). As an Azure Benefit Eligible partner, any spend on Neon Postgres via the Azure Marketplace helps fulfill your committed Azure spend with no extra steps required. Learn more.

Get usage notifications in Slack

You can now receive Neon usage notifications directly in your Slack channels! Get updates on your resource usage, find your projects, and invite team members to your organization - without leaving your workspace.

Neon Slack commands including new subscribe feature

Use /neon subscribe in any public channel to start receiving notifications, and /neon unsubscribe to turn them off. The bot will guide you through any necessary setup steps.

To learn more, see the Neon Slack App docs.

Fixes & improvements

  • Neon Console

    • Expanded the database drop-down menu width in the Neon SQL Editor to accommodate longer database names. Previously, longer names were not fully visible due to the narrow menu width.
    • Added an Unable to fetch projects message to the Projects page in the Neon Console. Previously, an error page was displayed when the project list couldn't be retrieved.

  • Autoscaling default settings

    We've updated the default autoscaling settings for newly created projects on paid Neon plans to provide a better balance of performance and efficiency:

    Neon planMinimum compute sizeMaximum compute size
    Launch14
    Scale18
    Business18

    These optimized defaults help ensure projects scale smoothly to meet workload demands while maintaining cost efficiency. This change applies only to newly created projects—existing projects and computes remain unaffected. You can review and adjust your autoscaling settings anytime in your project settings. From your Project Dashboard, go to Settings > Compute.

  • Postgres effective_cache_size setting is now optimized for better query plans

    Previously, Neon didn’t explicitly set the Postgres effective_cache_size Postgres parameter, so it defaulted to 4 GiB—often too low for larger compute sizes and autoscaling configurations. We now set this value based on the maximum size of Neon's Local File Cache (LFC) for a compute's maximum compute size, which helps the Postgres query planner make better decisions and improves query performance. For information about maximum LFC size per compute size, see the table in How to size your compute.

  • Neon API

  • Drizzle Studio update

    We updated the Drizzle Studio integration that powers the Tables page in the Neon Console to version 1.0.18. For the latest improvements and fixes, see the Neon Drizzle Studio Integration Changelog.

  • Fixes

    • Resolved an issue where resetting a role password in the Neon Console would result in an "invalid password" error in the SQL Editor and on the Tables page.
    • Revised the copy at the bottom of the Connect to your database modal for older Neon projects. The copy previously mentioned that passwords are stored, which is only true for Neon projects created after password storage was introduced.