Cloud SQL for PostgreSQL: Private Service Connect changes August 2026
Starting August 1, 2026, Cloud SQL for PostgreSQL instances enabled with Private Service Connect will have connection reconciliation enabled by default. This change will impact applications relying on Private Service Connect endpoints in projects that are later removed from the allowed list, as their connections will be immediately closed. This update applies to users creating, cloning, or enabling Private Service Connect on their instances.
Enhancements (1) ›
- Cloud SQL for PostgreSQL
Starting on August 1, 2026, when you create or clone a Cloud SQL instance enabled with Private Service Connect, or when you enable Private Service Connect for an existing instance, then connection reconciliation behavior is enabled by default and can't be disabled. When you remove a project from the list of allowed projects, all existing Private Service Connect connections from the removed project are immediately closed (reconciled). This means that applications using Private Service Connect endpoints in those removed projects can't continue to connect to the Cloud SQL instance using those end
https://docs.cloud.google.com/release-notes#July_31_2026
Related releases
- Cloud SQL for SQL Server 2017 Deprecation and End-of-Life Announced Google Cloud release notes ·
- Cloud SQL for PostgreSQL Adds `pg_textsearch` Extension for Full-Text Search Google Cloud release notes ·
- Cloud SQL for PostgreSQL: sqlcommenter tags temporarily disabled on remote MCP Google Cloud release notes ·
- Cloud SQL for MySQL: sqlcommenter Tag Appending Temporarily Disabled Google Cloud release notes ·
- Cloud SDK 584.0.0: Breaking Changes, Deprecations, and Security Update Google Cloud release notes ·
- Bridging the SQL Server Login Gap in Cloud SQL Migrations Google Cloud Blog ·