ReleaseBytes
gcp Google Cloud Blog ·

Google Cloud Spanner Removes Cumulative DML Transaction Limits

bloggcpgaengineerfinanceretailmediagcp-spanner
feature

Google Cloud Spanner has updated how DML transaction mutation limits are applied, shifting the 80,000 mutation mod cap from the entire transaction to individual DML statements. This enhancement allows applications to handle larger and more complex operational workloads, enabling developers to group DML statements logically without artificially splitting them. The change is compatible with existing client libraries, but larger transactions may increase lock contention and transaction aborts. The individual 80,000 mod limit still applies per DML statement, and other transaction constraints remain.

  • →Spanner DML mutation limit now per-statement
  • →Enhanced flexibility with operational considerations
Features (1) ›
  • Spanner DML mutation limit now per-statement

    Google Cloud Spanner has updated its DML transaction handling, shifting the 80,000 mutation mod limit from the entire transaction to individual DML statements. This allows a single transaction to contain any number of DML statements, such as INSERT, UPDATE, or DELETE, provided each individual statement generates fewer than 80,000 mods.

Notes (1) ›
  • Enhanced flexibility with operational considerations

    This change enables larger, more complex transactions without requiring application code updates, allowing DML statements to be grouped logically based on business requirements. However, larger and longer-running transactions may hold locks for a greater duration, potentially increasing lock contention and transaction aborts. The 80,000 mod limit still applies to individual DML statements and to the entire `Mutation API` commit call.

Read the original announcement →

https://cloud.google.com/blog/products/databases/spanner-removes-dml-mutation-limits/

Related releases