Optimistic transactions¶
In v4.2.5 optimistic transactions use snapshots, MVCC and conflict validation rather than acquiring pessimistic row locks at commit. The default is SI; confirm runtime configuration.
A concurrent committed modification can cause a conflict during write/commit validation and abort the transaction. Internal RC statement retries are not automatic optimistic transaction retries. Before restarting, applications must handle idempotency keys, external effects and whether the commit outcome is known.
See error boundaries and transaction usage.