
Spanner: Removing cumulative mutation limits for DML transactions
Google Cloud updated Spanner to shift the 80,000 mutation mod limit from total transactions to individual DML statements. This allows a single transaction to contain any number of DML statements.
Why it matters
Developers can now handle larger, more complex data updates without splitting transactions to avoid limits. This simplifies application logic for industries requiring high data consistency, such as banking and retail.
The big picture
This update improves Spanner, which prior coverage identifies as Google Cloud's operational database.
The details
Larger transactions may increase lock contention and transaction aborts. Mutation mods are calculated using modified cells, primary keys, and secondary index updates. The maximum transaction size in bytes remains unchanged. Users can monitor mutation counts via CommitStats.
Show entities and relationshipsHide entities and relationships
In this article
Companies
Products
Technologies
Key connections
Get the weekly recap
The stories like this one, picked and explained — once a week, straight to your inbox.