What's new
-
Added documentation for Neon's newly released Autoscaling feature. To learn how Neon automatically and transparently scales compute on demand, see Autoscaling. Pro users can enable Autoscaling when creating a Neon project or afterward by editing a compute endpoint. For instructions, see:
-
Added documentation for Neon's
pg_tiktokenextension. This extension enables fast and efficient tokenization of data in your PostgreSQL database using OpenAI's tiktoken library. To learn how to install the extension, utilize its features for tokenization and token management, and integrate the extension with ChatGPT models, see The pg_tiktoken extension. -
Added documentation for
pg_vectorextension. This extension enables vector similarity search and storing embeddings in PostgreSQL. It is particularly useful for applications involving natural language processing, such as those built on top of OpenAI's GPT models. For information about vector similarity and embeddings, how to enable thepgvectorextension in Neon, and how to create, store, and query vectors, see The pgvector extension. -
Reorganized our Prisma documentation into two parts to make it easier for you to get started with Prisma and Neon. The first part explains how to connect Prisma to Neon, establish connections when using Prisma Client with serverless functions, and resolve connection timeout issues. The second part describes how to configure Neon with Prisma Migrate for schema migrations.
-
Added documentation describing primary and non-primary branches. Each Neon project has a primary branch called
main, by default. The advantage of the primary branch is that its compute endpoint remains accessible if you exceed your project's limits, ensuring uninterrupted access to data that resides on the primary branch. Any branch not designated as the primary branch is considered a non-primary branch. To learn more, see: -
Added definitions for Neon operations to the glossary. An operation is an action performed by the Neon Control Plane on a Neon object or resource. Operations are typically initiated by user actions, such as creating a branch or deleting a database. Other operations are initiated by the Neon Control Plane, such as suspending a compute endpoint after a period of inactivity or checking its availability. You can monitor operations to keep an eye on the overall health of your Neon project or to check the status of specific operations. When working with the Neon API, you can poll the status of operations to ensure that an API request is completed before issuing the next API request. For more information, refer to our Operations documentation.
