Spanner release notes

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).

Spanner queues are generally available (GA). Spanner queues provide transactional messaging to help you manage asynchronous work. The feature pairs this capability with the scalability and reliability of Spanner, letting you build event-driven applications. For more information, see the Spanner queues overview.

Spanner Graph supports the following enhancements for CREATE PROPERTY GRAPH:

• Semantic options for labels and properties: You can configure OPTIONS (description and synonyms) on labels and properties to provide context and improve discoverability for natural language querying interfaces.
• Element key uniqueness validation option: You can configure the validate_element_key_uniqueness option in the property graph OPTIONS clause to control whether Spanner Graph validates element key uniqueness at schema creation time.

For more information, see CREATE PROPERTY GRAPH statement and Disabled key validation.

Spanner supports the following PostgreSQL-dialect database operators:

• ILIKE (~~*)
• NOT ILIKE (!~~*)

Spanner supports the following PostgreSQL-dialect database functions:

• pg.ilike
• pg.not_ilike

For more information, see Pattern matching operators and Functions.