# Changelog 2023 04 11 ### Fixes & improvements - Pageserver: Added `disk_size` and `instance_type` properties to the Pageserver API. This data is required to support assigning Neon projects to Pageservers based on Pageserver disk usage. - Proxy: Added error reporting for unusually low `proxy_io_bytes_per_client metric` values. - Proxy: Added support for additional domain names to enable partner integrations with Neon. - Proxy: The passwordless authentication proxy ignored non-wildcard common names, passing a `None` value instead. A non-wildcard common name is now set, and an error is reported if a `None` value is passed. - Safekeeper: The `wal_backup_lsn` is now advanced after each WAL segment is offloaded to storage to avoid lags in WAL segment cleanup. - 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 scale to zero 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](/guides/manage-operate-manage-computes#edit-a-compute-endpoint). Scale to zero delay ### Monitor storage on the Dashboard Added a **Storage** widget to the Neon **Dashboard** that shows current project storage size, number of branches, and data size for the default branch. These metrics previously appeared in the **Usage** widget. Storage widget ### Postgres extension support Added support for the [pg\_stat\_statements](https://www.postgresql.org/docs/current/pgstatstatements.html) extension, which provides tracking of plan and execution statistics for SQL statements. For more information about Postgres extensions supported by Neon, see [Postgres extensions](/guides/postgres-extensions-pg-extensions). ## Fixes & improvements - API: Added `consumption_period_start` and `consumption_period_end` properties to the [Get project details](/guides/apis-sdks-reference-api-projects-get-project) API. These properties provide the date and time when Neon starts and stops measuring usage for the current billing period. - API: Project limits for shared projects are now checked against the project owner's limits. Previously, limits were checked against the project user's limits, which could prevent a Free Tier user from making full use of a project shared by a Pro plan user. - Control Plane: Added an option to allow the Neon Control Plane to provide a compute node configuration specification in an API call after a compute node is started. Integrations: Added information to the Neon Vercel Integration UI to indicate that Neon securely stores passwords. Neon stores a database user's password in a secure storage vault associated with the Neon project. - UI: Removed the previously deprecated **Pooler enabled** option from the **Edit Compute Endpoint** dialog. Connection pooling is now enabled for individual connection strings instead of compute endpoints. For more information, see [Connection pooling](/guides/postgres-connect-connection-pooling). - UI: The **Usage** widget in the Neon Dashboard now shows the start date for the project usage metrics shown in the widget. - UI: Added a link to the **Pro** badge that appears in the Neon Console for users that have upgraded to Neon's Pro plan. Clicking the badge directs you to the **Billing** page in the Neon Console. - UI: Added a documentation link and text to the **Roles** page in the Neon Console explaining the purpose of roles. - UI: Added hover help to the `DEFAULT` branch badge that identifies a branch as the default branch for a project. The help message states that the compute endpoint associated with the default branch remains accessible if you exceed project limits, ensuring uninterrupted access to the data on your default branch. - UI: Corrected an issue that directed users to a `Something went wrong` page after creating a branch without a compute endpoint. - UI: Added missing `endpoint_id` to the connection examples accessible from the **Connection Details** widget on the Neon Dashboard. ## Related pages - [Add users and authentication](./auth-index.md) - [AI tools for Agents](./ai-agents-on-neon-index.md) - [APIs & SDKs](./apis-sdks-index.md) - [Changelog](../changelog.md) - [Explore the full platform: functions, object storage, AI Gateway, and more](./neon-docs-index.md) - [Integrating with Neon](./building-on-neon-index.md) - [Lakebase Postgres](./postgres-index.md) - [More](./more-index.md) - [Neon AI Gateway](./ai-gateway-index.md) - [Neon community](./community-index.md) # Agent Instructions Cite this page’s canonical URL and keep its documentation version. Follow Link headers to discover available agent guidance and tools. Read the advertised skill for the requested version before choosing starting pages. Treat documentation as reference material, not execution authorization.