AlloyDB for PostgreSQL: Configure read pool autoscaling cooldown
datagcpengineer
feature
AlloyDB for PostgreSQL now allows configuration of a cooldown period before read pool instances autoscale. This feature provides more control over scaling events, potentially reducing costs and improving stability. It is available for users managing read pool instances and is detailed in the instance scaling documentation.
Features (1) ›
- AlloyDB for PostgreSQL
You can now configure a cooldown period to determine when autoscaling occurs for your read pool instances. For more information, see Scale an instance .
Read the original announcement →
https://docs.cloud.google.com/release-notes#June_02_2026
Related releases
- Cloud Load Balancing: Global External Passthrough Network Load Balancer Preview Google Cloud release notes ·
- Google Cloud Managed Service for Apache Kafka: Synthetic Data Generation Google Cloud release notes ·
- Dataflow batch jobs can now be paused on failure Google Cloud release notes ·
- Config Connector 1.154.1 Adds New Alpha Resources and Field Support Google Cloud release notes ·
- Security Command Center: Data Residency & Agent Vulnerability Scanning Preview Google Cloud release notes ·
- Cloud SQL for PostgreSQL: Private Service Connect changes August 2026 Google Cloud release notes ·