You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
sql: add exponential backoff to read committed stmt retry loop
Testing has shown that adding exponential backoff significantly improves
throughput of highly contentious read committed workloads.
Informs: #145377
Release note (sql change): Add session variable
`initial_retry_backoff_for_read_committed` which controls the initial
backoff duration when retrying an individual statement in an explicit
READ COMMITTED transaction. A duration of 0 disables exponential
backoff.
If a statement in an explicit READ COMMITTED transaction is failing with
the following 40001 error:
```
ERROR: restart transaction: read committed retry limit exceeded; set by max_retries_for_read_committed=...
```
Then `initial_retry_backoff_for_read_committed` should be set to a
duration proportional to the typical execution time of the statement (in
addition to also increasing `max_retries_for_read_committed`).
0 commit comments