Merge branch 'main' into dprice-use-case-content

content/changelog/2023-03-15.md

@@ -7,7 +7,7 @@ redirectFrom:
 
 In addition to the [Free Tier](/docs/introduction/free-tier), Neon now offers the following paid plans:
 
-- **Pro**: A usage-based plan, ideal for small-to-medium teams. With the Pro plan, you get up to 20 projects, unlimited branches, unlimited compute time, up to 200 GiB of storage, and access to paid plan features such as project sharing, autoscaling (_coming soon_), and configurable autosuspend compute (_coming soon_).
+- **Pro**: A usage-based plan, ideal for small-to-medium teams. With the Pro plan, you get up to 20 projects, unlimited branches, unlimited compute time, up to 200 GiB of storage, and access to paid plan features such as project sharing, autoscaling (_coming soon_), and configurable scale to zero (_coming soon_).
 - **Enterprise**: A volume-based plan for medium-to-large teams and database fleets. Includes all Pro plan features plus customized limits and potential for volume discounts.
 - **Platform Partnership**: A volume-based plan for large teams, database fleets, and resale. Includes all Enterprise plan features plus resale support.
 

content/changelog/2023-04-11.md

@@ -14,10 +14,10 @@ redirectFrom:
 - Safekeeper: Added a timeout for reading from the socket in the Safekeeper WAL service to avoid an accumulation of waiting threads.
 - Pageserver: Corrected an issue that caused data layer eviction to occur at a percentage above the configured disk-usage threshold.
 
-### Configurable autosuspend
+### Configurable scale to zero
 
-You can now configure the period of inactivity after which a compute is automatically suspended by modifying the **Suspend compute after a period of inactivity** setting for a compute endpoint. For example, you can increase the setting to reduce how often a compute is suspended, or you can disable the feature entirely to ensure that a compute remains active. The maximum autosuspend setting is 86400 seconds (24-hours). A setting of 0 means use the default (5 minutes / 300 seconds), and a setting of -1 means never suspend the compute. You can access the configuration dialog by [editing a compute endpoint](/docs/manage/endpoints#edit-a-compute-endpoint).
-![Autosuspend delay](/docs/relnotes/auto_suspend_delay.png)
+You can now configure the period of inactivity after which a compute is automatically suspended. For example, you can increase the setting to reduce how often a compute is suspended, or you can disable the feature entirely to ensure that a compute remains active. The maximum scale to zero setting is 86400 seconds (24-hours). A setting of 0 means use the default (5 minutes / 300 seconds), and a setting of -1 means never suspend the compute. You can access the configuration dialog by [editing a compute endpoint](/docs/manage/endpoints#edit-a-compute-endpoint).
+![Scale to zero delay](/docs/relnotes/auto_suspend_delay.png)
 
 ### Monitor storage on the Dashboard
 

content/changelog/2023-04-28.md

@@ -9,9 +9,9 @@ redirectFrom:
 
 - API: Enabled checking for the Neon API specification to ensure that examples are updated when the specification is modified.
 - API: Added a `history_retention_seconds` property to the [Project](https://api-docs.neon.tech/reference/getproject) response body. Neon retains a 7-day history to support point-in-time restore. History retention will become a configurable parameter in a future release.
-- API: Increased the maximum value of the `suspend_timeout_seconds` property in the [Endpoint](https://api-docs.neon.tech/reference/getprojectendpoint) API from 86400 seconds (1 day) to 604800 seconds (7 days). This change affects the maximum autosuspend setting that Neon Pro plan users can configure when creating or editing a compute endpoint. The autosuspend setting defines the number of seconds of inactivity after which a compute endpoint is automatically suspended. The default is 300 seconds (5 minutes). For more information, see [Autosuspend configuration](/docs/manage/endpoints#auto-suspend-configuration).
+- API: Increased the maximum value of the `suspend_timeout_seconds` property in the [Endpoint](https://api-docs.neon.tech/reference/getprojectendpoint) API from 86400 seconds (1 day) to 604800 seconds (7 days). This change affects the maximum scale to zero setting that Neon Pro plan users can configure when creating or editing a compute endpoint. The scale to zero setting defines the number of seconds of inactivity after which a compute endpoint is automatically suspended. The default is 300 seconds (5 minutes). For more information, see [Scale to zero configuration](/docs/manage/endpoints#scale-to-zero-configuration).
 - Control Plane: Added a constraint to ensure that the maximum autoscaling compute size is greater than or equal to the minimum compute size.
-- UI: Redesigned the branch details page in the Neon Console. In addition to the information displayed previously, the page now provide usage metrics, including **Active time**, **Compute time**, **Written data**, and **Data transfer**. This information enables you to monitor usage for individual branches. Refer to our [Billing](/docs/introduction/about-billing) page for information about the usage metrics. The compute endpoint information on the branch details page has also been expanded to include **Compute size**, **Autosuspend delay**, and **Last active** information. **Compute size (min)** and **Compute size (max)** values are shown for computes with the [Autoscaling](/docs/introduction/autoscaling) feature enabled. For information about these values, see [View a compute endpoint](/docs/manage/endpoints#view-a-compute-endpoint).
+- UI: Redesigned the branch details page in the Neon Console. In addition to the information displayed previously, the page now provide usage metrics, including **Active time**, **Compute time**, **Written data**, and **Data transfer**. This information enables you to monitor usage for individual branches. Refer to our [Billing](/docs/introduction/about-billing) page for information about the usage metrics. The compute endpoint information on the branch details page has also been expanded to include **Compute size**, **Scale to zero delay**, and **Last active** information. **Compute size (min)** and **Compute size (max)** values are shown for computes with the [Autoscaling](/docs/introduction/autoscaling) feature enabled. For information about these values, see [View a compute endpoint](/docs/manage/endpoints#view-a-compute-endpoint).
 - UI: Added an **Active time** column to the table on the **Branches** page in the Neon Console. This column shows the number of hours the branch compute endpoint has been active for the current month.
 - UI: The **Connection Details** dialog displayed when creating a project or a branch now provides **Pooled connection** and **Direct connection** tabs, allowing you to copy a pooled or direct connection string for the ready-to-use `neondb` database. For information about connection pooling in Neon, see [Connection pooling](/docs/connect/connection-pooling).
 - UI: Updated the `prisma.js` code example accessible from the **Connection Details** widget on the Neon **Dashboard**. The connection string now includes a `connect_timeout` parameter to prevent Prisma from timing out due to cold starts, and a `pgbouncer=true` parameter, which is required when using Prisma with a pooled connection string. For more information about using Neon with Prisma, see [Connect Neon to Prisma](/docs/guides/prisma).

content/changelog/2023-05-16.md

@@ -14,7 +14,7 @@ redirectFrom:
 - API: The [Update endpoint](https://api-docs.neon.tech/reference/updateprojectendpoint) API now permits moving an endpoint from one branch to another without specifying `autoscaling_limit_max_cu` and `autoscaling_limit_min_cu` property values, which should not be required when performing this action.
 - Control Plane: Neon plan limits are now transmitted when using [passwordless authentication](/docs/connect/passwordless-connect), enabling users logging in via this method to create projects, in accordance with their plan limits.
 - UI: Fixed an issue that prevented Free Tier users from creating a compute endpoint for an existing branch. The **Fixed size** compute setting in the **Create Compute Endpoint** modal defaulted to 1 vCPU, which exceeded the Free Tier compute size limit.
-- UI: Fixed the **Autosuspend delay** control on the **Create Compute Endpoint** and **Edit Compute Endpoint** modals to permit values up to 604800 seconds (7 days). The limit was recently increased from 86400 seconds (1 day).
+- UI: Fixed the **Scale to zero delay** control on the **Create Compute Endpoint** and **Edit Compute Endpoint** modals to permit values up to 604800 seconds (7 days). The limit was recently increased from 86400 seconds (1 day).
 - UI: Fixed issues with how icons were displayed in the **Usage** widget on the **Neon Dashboard**.
 
 ### Fixes & improvements

content/changelog/2023-07-24.md

@@ -3,10 +3,10 @@ redirectFrom:
   - /docs/changelog/2023-07-24-console
 ---
 
-### Autosuspend delay project defaults
+### Scale to zero delay project defaults
 
-Neon now provides an **Autosuspend delay** control on the project creation dialog, enabling Neon Pro plan users to define a default autosuspend setting for a project's compute endpoints. The autosuspend setting defines the period of inactivity after which a compute endpoint is automatically suspended. For more information, see [Create a project](/docs/manage/projects#create-a-project).
-![Autosuspend delay project creation dialog](/docs/relnotes/auto_suspend_delay_create_project.png)
+Neon now provides an **Scale to zero delay** control on the project creation dialog, enabling Neon Pro plan users to define a default scale to zero setting for a project's compute endpoints. The scale to zero setting defines the period of inactivity after which a compute endpoint is automatically suspended. For more information, see [Create a project](/docs/manage/projects#create-a-project).
+![Scale to zero delay project creation dialog](/docs/relnotes/auto_suspend_delay_create_project.png)
 
 ### Fixes & improvements
 

content/changelog/2023-07-25.md

@@ -5,7 +5,7 @@ redirectFrom:
 
 ### Faster cold starts in all regions
 
-Neon's _Autosuspend_ feature scales a compute instance to zero after a period of inactivity. A characteristic of this feature is a "cold start", which occurs when an idle compute is restarted to process requests. Recently, cold-start times have been improved through a variety of enhancements, outlined below:
+Neon's _Scale to Zero_ feature scales a compute instance to zero after a period of inactivity. A characteristic of this feature is a "cold start", which occurs when an idle compute is restarted to process requests. Recently, cold-start times have been improved through a variety of enhancements, outlined below:
 
 - **Compute pools**: Instead of starting computes from zero, requests for computes are now served from pools of pre-started compute instances.
 - **Compute configuration optimization**: Configuration changes at compute startup were eliminated where possible.
@@ -15,4 +15,4 @@ Neon's _Autosuspend_ feature scales a compute instance to zero after a period of
 
 With these improvements, cold starts are faster in all [supported regions](/docs/introduction/regions). Cold starts in the `US East (Ohio) — aws-us-east-2` region, where the Neon Control Plane is hosted, are the fastest at approximately 500 ms. Work is underway to deploy the Neon Control Plane regionally to enable the same millisecond startup times for projects in all regions. For more information about this effort, please check out the blog post from the Neon engineering team: [Cold starts just got hot](https://neon.tech/blog/cold-starts-just-got-hot).
 
-Please be aware that [Neon Pro plan](/docs/introduction/pro-plan) users can adjust or disable the [Autosuspend](/docs/guides/auto-suspend-guide) setting, controlling when a compute scales to zero. Additionally, Neon's [Autoscaling](/docs/guides/autoscaling-guide) feature allows you to scale compute resources down to a fractional size during periods of low activity.
+Please be aware that [Neon Pro plan](/docs/introduction/pro-plan) users can adjust or disable the [scale to zero](/docs/guides/scale-to-zero-guide) setting, controlling when a compute scales to zero. Additionally, Neon's [Autoscaling](/docs/guides/autoscaling-guide) feature allows you to scale compute resources down to a fractional size during periods of low activity.

content/changelog/2023-08-09.md

@@ -10,9 +10,9 @@ You can now configure the history retention period for a Neon project. History r
 The **History retention** setting is located in the Neon Console under **Project settings** > **Storage**.
 ![History retention configuration](/docs/relnotes/history_retention.png)
 
-### Configurable Autosuspend
+### Configurable Scale to zero
 
-After an extensive testing period, we are pleased to announce that our _Configurable autosuspend_ feature has successfully transitioned out of Beta. This feature controls when a Neon compute instance scales to zero due to inactivity. For more information, see [Configuring Autosuspend for Neon computes](/docs/guides/auto-suspend-guide).
+After an extensive testing period, we are pleased to announce that our _Configurable scale to zero_ feature has successfully transitioned out of Beta. This feature controls when a Neon compute instance scales to zero due to inactivity. For more information, see [Configuring Scale to zero for Neon computes](/docs/guides/scale-to-zero-guide).
 
 ### Fixes & improvements
 

content/changelog/2023-08-14.md

@@ -7,4 +7,4 @@ redirectFrom:
 
 - UI: Revised the Free Tier **Billing** page design where users can view [Free Tier](/docs/introduction/free-tier) limits and learn about the benefits of upgrading to the [Neon Pro plan](/docs/introduction/pro-plan). The **Billing** page is accessible from the sidebar in the Neon Console.
 - UI: Fixed the code example drop-down menu on the **Connection Details** widget on the Neon **Dashboard**. The menu now opens above the selector if there is not enough space in the browser window for the menu to drop down.
-- UI: The **Project Creation** modal now displays an error for invalid **Autosuspend** delay settings.
+- UI: The **Project Creation** modal now displays an error for invalid **Scale to zero** delay settings.

content/changelog/2023-09-08.md

@@ -5,7 +5,7 @@ redirectFrom:
 
 ### Configure default compute settings for your project
 
-[Pro plan](/docs/introduction/pro-plan) users can now configure default compute settings for a Neon project. Settings include **Compute size**, **Autoscaling**, and **Autosuspend delay**. To define defaults, select **Project settings** > **Compute** from the Neon **Dashboard** to open the **Default compute settings** page. For [Free Tier](/docs/introduction/free-tier) users, the page shows the default settings.
+[Pro plan](/docs/introduction/pro-plan) users can now configure default compute settings for a Neon project. Settings include **Compute size**, **Autoscaling**, and **Scale to zero delay**. To define defaults, select **Project settings** > **Compute** from the Neon **Dashboard** to open the **Default compute settings** page. For [Free Tier](/docs/introduction/free-tier) users, the page shows the default settings.
 ![Default compute settings](/docs/relnotes/default_compute_settings.png)
 
 Default settings are applied when creating a branch or adding a compute to a branch via the Neon Console. However, if you want a compute with different settings, you can change or override the defaults when creating a branch or adding a compute.

content/changelog/2023-10-17.md

@@ -5,13 +5,13 @@ redirectFrom:
 
 ### Fixes & improvements
 
-- UI: Added new fields for configuring the autosuspend delay period for Neon compute instances, allowing you to specify the delay period in seconds, minutes, hours, or days.
+- UI: Added new fields for configuring the scale to zero delay period for Neon compute instances, allowing you to specify the delay period in seconds, minutes, hours, or days.
 
-  ![Autosuspend delay controls](/docs/relnotes/autosuspend_controls.png)
+  ![Scale to zero delay controls](/docs/relnotes/autosuspend_controls.png)
 
-  Neon's _Autosuspend_ feature automatically suspends a compute endpoint after a period of inactivity to minimize compute costs. This feature is also known as "scale-to-zero". By default, suspension occurs after 5 minutes of inactivity. [Neon Pro Plan](/docs/introduction/pro-plan) users can configure the autosuspend setting when creating a project, changing default compute settings, creating a compute endpoint, or editing a compute endpoint.
+  Neon's _Scale to Zero_ feature automatically suspends a compute endpoint after a period of inactivity to minimize compute costs. This feature is also known as "scale-to-zero". By default, suspension occurs after 5 minutes of inactivity. [Neon Pro Plan](/docs/introduction/pro-plan) users can configure the scale to zero setting when creating a project, changing default compute settings, creating a compute endpoint, or editing a compute endpoint.
 
-  For more information about this feature, see [Autosuspend](/docs/introduction/auto-suspend).
+  For more information about this feature, see [Scale to Zero](/docs/introduction/scale-to-zero).
 
 - UI: When sharing a Neon project with someone who does not have a Neon account, an email invitation is now sent to the specified email address. Previously, an email was only sent to registered Neon users.
 

content/changelog/2024-01-19.md

@@ -26,7 +26,7 @@ The [Neon CLI](/docs/reference/neon-cli) now includes an `ip-allow` command, whi
 - 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](/docs/manage/integrations#express-interest-in-upcoming-integrations).
 - Added a dialog requiring user confirmation when removing all IP addresses from an [IP Allow](/docs/introduction/ip-allow) configuration.
 - The **Community** link in the Neon Console sidebar has been updated to direct users to the [Neon Discord](https://discord.com/invite/92vNTzKDGp) server, rather than the [Neon Discourse forum](https://community.neon.tech/).
-- 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 prevent connection errors at the subscriber and repeated compute restarts, Neon no longer suspends 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.

content/changelog/2024-01-26.md

@@ -60,4 +60,4 @@ We are excited to announce the launch of our [Success Stories](https://neon.tech
 In case you missed them, be sure to check out our latest blog posts:
 
 - [See you at FOSDEM and FOSDEM PGDay 2024](https://neon.tech/blog/see-you-at-fosdem-and-fosdem-pgday-2024)
-- [Using Neon’s Auto-Suspend with Long-Running Applications](https://neon.tech/blog/using-neons-auto-suspend-with-long-running-applications)
+- [Using Neon’s Scale to Zero with Long-Running Applications](https://neon.tech/blog/using-neons-auto-suspend-with-long-running-applications)