Skip to content

Commit

Permalink
Merge pull request #2821 from neondatabase/docs-changelog-2025-01-24
Browse files Browse the repository at this point in the history
changelog 2025-01-24
  • Loading branch information
danieltprice authored Jan 24, 2025
2 parents cb1b5aa + ef023bc commit e658ceb
Show file tree
Hide file tree
Showing 8 changed files with 125 additions and 42 deletions.
83 changes: 83 additions & 0 deletions content/changelog/2025-01-24.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,83 @@
---
description: Neon Chat for VS Code, scheduled updates coming soon, and more
---

### Neon Chat for Visual Studio Code

The [Neon Chat for Visual Studio Code](https://marketplace.visualstudio.com/items?itemName=buildwithlayer.neon-integration-expert-15j6N) extension is now available in the GitHub Marketplace. This AI-powered assistant lets you chat with the latest Neon documentation without leaving your IDE.

Get answers to common questions like:

- _How to create a project?_
- _How can I get started with the Neon API?_
- _How do I create a branch using the Neon CLI?_

![Neon Chat for Visual Studio Code](/docs/relnotes/neon_chat_visual_studio.png)

### Scheduled updates coming soon 📅

Neon is introducing scheduled updates, starting with Free Plan accounts and later expanding to Paid Plans. These updates will cover Postgres updates, security patches, and Neon feature enhancements, automatically applied to your project's computes. Here's what to expect:

- Updates aren’t new, but now they’ll be scheduled so you’ll know when they’re coming and won't fall behind on important maintenance.
- Updates require a compute restart, but restarts are quick and automatic — taking just a few seconds.
- If your computes scale to zero & restart regularly, available updates will be applied on compute restart, removing the need for "scheduled" updates.
- You’ll be able to track scheduled updates in your project settings.
- Free Plan accounts will have updates scheduled in advance for a specific day and time, while Paid Plan accounts will be able to choose a preferred update window.

Stay tuned for specific details about when scheduled updates will roll out. Free Plan users can expect to see scheduled updates first, starting in early February. Scheduled updates on Paid Plans will roll out later, with updates for large compute sizes (> 8 CU) rolling out last.

### Connect to external Postgres databases with the `dblink` extension

Neon now supports accessing external Postgres databases using the [dblink](https://www.postgresql.org/docs/current/contrib-dblink-function.html) extension. `dblink` lets you easily connect to other Postgres databases and run queries on them. It's a good choice for quick, one-off queries or situations where you need data from a remote database but don’t want to configure a foreign data wrapper.

### Support for the `pg_repack` extension

The Postgres [pg_repack](https://reorg.github.io/pg_repack/) extension is now available on paid Neon plans upon request. This extension helps you remove bloat from tables and indexes while optionally restoring the physical order of clustered indexes — all without requiring an exclusive lock during processing. This extension is currently available only on paid Neon plans. To enable `pg_repack`, [open a support ticket](https://console.neon.tech/app/projects?modal=support) and include your endpoint ID and the database name where you'd like the extension enabled.

### Meet "Instagres": No signup, instant Postgres ✨

Neon's architecture lets us do some pretty interesting things, like creating a Postgres database in less than a second (AI agents loves this, btw). To showcase this ability, we've built "Instagres," an app that lets you generate a Postgres database URL almost instantly — no sign up required. If you'd like to keep the database for more than an hour, you can transfer it to your Neon account.

![Instagres UI](/docs/relnotes/instagres.png)

Give it a try at [https://www.instagres.com/](https://www.instagres.com/) or by running `npx instagres` in your terminal.

The "Instagres" app is powered by Cloudflare, React Router, and DrizzleORM.

If you like this feature or see different use cases for it, please let us know via the [Feedback](https://console.neon.tech/app/projects?modal=feedback) form in the Neon Console or our [feedback channel](https://discord.com/channels/1176467419317940276/1176788564890112042) on Discord.

To learn more, read the [blog post](https://neon.tech/blog/launch-postgres-in-your-browser-keep-it-on-neon).

### Pooled connection strings are now default in the Neon Console

[Pooled connection strings](/docs/connect/connection-pooling) are now the default in the **Connection Details** widget in the Neon Console. Pooled connection strings include a `-pooler` option, which directs connections to a pooled connection port powered by PgBouncer. With support for up to 10,000 concurrent connections, connection pooling improves performance, reduces latency, and makes resource management more efficient for most applications. For specific tasks like `pg_dump` and other session-dependent operations like schema migrations, you can still get direct connection string at any time by disabling the connection pooling toggle in the **Connection Details** widget or by removing `-pooler` from your connection string manually.

![pooled connection string](/docs/relnotes/connection_pooler.png)

## A new version of the Neon Python SDK

Neon's [Python SDK](https://pypi.org/project/neon-api/), which is a wrapper for the [Neon API](https://api-docs.neon.tech/reference/getting-started-with-neon-api), has been updated to a new version (0.3.0). This new version updates the Python data types from Neon's API schema.

This SDK simplifies integration of Python applications with Neon by providing methods to programmatically manage Neon API keys, projects, branches, databases, endpoints, roles, and operations.

<details>

<summary>**Fixes & improvements**</summary>

- **Drizzle Studio update**

The Drizzle Studio integration that powers the **Tables** page in the Neon Console has been updated to version 1.0.11. For the latest improvements and fixes, see the [Neon Drizzle Studio Integration Changelog](https://github.com/neondatabase/neon-drizzle-studio-changelog/blob/main/CHANGELOG.md).

- **Console updates**

**Increased concurrency limits**. Last week we announced increased Neon API operation concurrency limits on Neon's Free, Launch, and Scale plans. **This enhancement is now supported on all Neon plans**.

As noted in last week's changelog: Previously, concurrent API operations within a Neon project — such as operations on different branches — could trigger a "project already has running operations" error, where one branch operation would block others. This improvement reduces the need to work around strict concurrency limits. However, we still recommend adding retry functionality to handle rare cases where an API operation fails due to ongoing operations.

This change applies only to the Neon API. In the Neon Console, controls such as buttons that initiate new operations are still briefly disabled until ongoing operations are complete. Concurrency improvements will be reflected in the UI in a future release.

- **Fixes**

Fixed an issue with the **Create branch** button in the Neon Console. Previously, the button became disabled for unfinished project operations, including those that failed due to an error. Now, the button is disabled only for project operations in the canceling, running, or scheduling state.

</details>
80 changes: 40 additions & 40 deletions content/docs/connect/connection-pooling.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,46 +29,46 @@ The `-pooler` option routes the connection to a connection pooling port at the N

Each Postgres connection creates a new process in the operating system, which consumes resources. Postgres limits the number of open connections for this reason. The Postgres connection limit is defined by the Postgres `max_connections` parameter. In Neon, `max_connections` is set according to your compute size &#8212; and if you are using Neon's Autoscaling feature, it is set according to your **maximum** compute size.

| Max. Compute Size (CU) | vCPU | RAM | max_connections |
| :--------------------- | :--- | :----- | :-------------- |
| 0.25 | 0.25 | 1 GB | 112 |
| 0.50 | 0.50 | 2 GB | 225 |
| 1 | 1 | 4 GB | 450 |
| 2 | 2 | 8 GB | 901 |
| 3 | 3 | 12 GB | 1351 |
| 4 | 4 | 16 GB | 1802 |
| 5 | 5 | 20 GB | 2253 |
| 6 | 6 | 24 GB | 2703 |
| 7 | 7 | 28 GB | 3154 |
| 8 | 8 | 32 GB | 3604 |
| 9 | 9 | 36 GB | 4000 |
| 10 | 10 | 40 GB | 4000 |
| 11 | 11 | 44 GB | 4000 |
| 12 | 12 | 48 GB | 4000 |
| 13 | 13 | 52 GB | 4000 |
| 14 | 14 | 56 GB | 4000 |
| 15 | 15 | 60 GB | 4000 |
| 16 | 16 | 64 GB | 4000 |
| 18 | 18 | 72 GB | 4000 |
| 20 | 20 | 80 GB | 4000 |
| 22 | 22 | 88 GB | 4000 |
| 24 | 24 | 96 GB | 4000 |
| 26 | 26 | 104 GB | 4000 |
| 28 | 28 | 112 GB | 4000 |
| 30 | 30 | 120 GB | 4000 |
| 32 | 32 | 128 GB | 4000 |
| 34 | 34 | 136 GB | 4000 |
| 36 | 36 | 144 GB | 4000 |
| 38 | 38 | 152 GB | 4000 |
| 40 | 40 | 160 GB | 4000 |
| 42 | 42 | 168 GB | 4000 |
| 44 | 44 | 176 GB | 4000 |
| 46 | 46 | 184 GB | 4000 |
| 48 | 48 | 192 GB | 4000 |
| 50 | 50 | 200 GB | 4000 |
| 52 | 52 | 208 GB | 4000 |
| 54 | 54 | 216 GB | 4000 |
| 56 | 56 | 224 GB | 4000 |
| Compute size | vCPU | RAM | max_connections |
| :----------- | :--- | :----- | :-------------- |
| 0.25 | 0.25 | 1 GB | 112 |
| 0.50 | 0.50 | 2 GB | 225 |
| 1 | 1 | 4 GB | 450 |
| 2 | 2 | 8 GB | 901 |
| 3 | 3 | 12 GB | 1351 |
| 4 | 4 | 16 GB | 1802 |
| 5 | 5 | 20 GB | 2253 |
| 6 | 6 | 24 GB | 2703 |
| 7 | 7 | 28 GB | 3154 |
| 8 | 8 | 32 GB | 3604 |
| 9 | 9 | 36 GB | 4000 |
| 10 | 10 | 40 GB | 4000 |
| 11 | 11 | 44 GB | 4000 |
| 12 | 12 | 48 GB | 4000 |
| 13 | 13 | 52 GB | 4000 |
| 14 | 14 | 56 GB | 4000 |
| 15 | 15 | 60 GB | 4000 |
| 16 | 16 | 64 GB | 4000 |
| 18 | 18 | 72 GB | 4000 |
| 20 | 20 | 80 GB | 4000 |
| 22 | 22 | 88 GB | 4000 |
| 24 | 24 | 96 GB | 4000 |
| 26 | 26 | 104 GB | 4000 |
| 28 | 28 | 112 GB | 4000 |
| 30 | 30 | 120 GB | 4000 |
| 32 | 32 | 128 GB | 4000 |
| 34 | 34 | 136 GB | 4000 |
| 36 | 36 | 144 GB | 4000 |
| 38 | 38 | 152 GB | 4000 |
| 40 | 40 | 160 GB | 4000 |
| 42 | 42 | 168 GB | 4000 |
| 44 | 44 | 176 GB | 4000 |
| 46 | 46 | 184 GB | 4000 |
| 48 | 48 | 192 GB | 4000 |
| 50 | 50 | 200 GB | 4000 |
| 52 | 52 | 208 GB | 4000 |
| 54 | 54 | 216 GB | 4000 |
| 56 | 56 | 224 GB | 4000 |

The formula used to calculate `max_connections` for Neon computes is `RAM in bytes / 9531392 bytes`. For a Neon Free Plan compute, which has 1 GB of RAM, this works out to approximately 112 connections. Larger computes offered with paid plans have more RAM and therefore support a larger number of connections. For example, a compute with 12 GB of RAM supports up to 1351 connections. You can check the `max_connections` limit for your compute by running the following query from the Neon SQL Editor or a client connected to Neon:

Expand Down
2 changes: 1 addition & 1 deletion content/docs/guides/vercel-native-integration.md
Original file line number Diff line number Diff line change
Expand Up @@ -143,7 +143,7 @@ To create another Database / Neon Project:
1. On the Vercel Dashboard, navigate to your **Integrations** tab.
2. Locate the **Neon Postgres** integration, and click **Manage**.
3. Find the **More Products** card, and click **Install**.
4. Make your selections for region, compute size settings, and plan on the **Create Database** modal, and click **Continue**.
4. Make your selections for the region, scale to zero suspend time, and plan on the **Create Database** modal, and click **Continue**. For more about scale to zero, see [Scale to zero](/docs/introduction/scale-to-zero). Only the **Default** suspend setting is supported on the Free Plan.

<Admonition type="note">
Remember, if you're adding another "Database", you're' already on a Neon Plan, which will be identified on the modal by a **Current** tag. Select a different plan will change your Neon Plan for all of your "Databases". So, don't select a different plan unless you actually want to change your plan for all of your "Databases".
Expand Down
2 changes: 1 addition & 1 deletion content/docs/manage/endpoints.md
Original file line number Diff line number Diff line change
Expand Up @@ -551,7 +551,7 @@ You may encounter an error similar to the following when your compute's local di
ERROR: could not write to file "base/pgsql_tmp/pgsql_tmp1234.56.fileset/o12of34.p1.0": No space left on device (SQLSTATE 53100)
```

Neon computes allocate approximately 20 GB of local disk space for temporary files used by Postgres. Data-intensive operations can sometimes consume all of this space, resulting in `No space left on device` errors.
Neon computes allocate 20 GiB of local disk space or 15 GiB x the maximum compute size (whichever is highest) for temporary files used by Postgres. Data-intensive operations can sometimes consume all of this space, resulting in `No space left on device` errors.

To resolve this issue, you can try the following strategies:

Expand Down
Binary file added public/docs/relnotes/connection_pooler.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added public/docs/relnotes/instagres.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added public/docs/relnotes/neon_chat_visual_studio.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added public/docs/relnotes/slack_app.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.

0 comments on commit e658ceb

Please sign in to comment.