Google Cloud Spanner Automatically Parameterizes SQL Query Literals for Performance
Google Cloud Spanner now supports automatic parameterization of SQL query literals, enhancing performance and reducing CPU costs. This feature converts hardcoded literal values in CRUD-style queries, such as primary key lookups and joins, into query parameters. By enabling the caching and reuse of execution plans, it helps lower latency and operational expenses. Spanner users running applications with such queries can benefit from improved efficiency.
Features (1) ›
- Spanner
Spanner supports automatic parameterization of SQL query literals to improve query performance, reduce latency, and lower CPU costs. Spanner converts literal values hardcoded in CRUD-style queries, such as primary key lookups, index lookups, and primary key joins, into query parameters, allowing execution plans to be cached and reused to reduce latency and CPU costs. For more information, see Use query parameters and statement hints ( GoogleSQL and PostgreSQL ).
https://docs.cloud.google.com/release-notes#September_18_2026
Related releases
- Spanner Queues Now Generally Available for Transactional Messaging Google Cloud release notes ·
- Spanner Graph Enhancements Improve Querying and Schema Validation Google Cloud release notes ·
- Google Cloud Introduces Autonomous Network Operations Framework for Telcos Google Cloud Blog ·
- Google Cloud Spanner Removes Cumulative DML Transaction Limits Google Cloud Blog ·
- Google Finance Engineering Automates Spanner Dual-Write Migrations Google Cloud Blog ·
- Spanner Adds PostgreSQL-Dialect ILIKE and NOT ILIKE Operators Google Cloud release notes ·