As part of fixing #21361, query layer retries were blocked for multi-statement queries via simple query protocol since a query could have multiple transaction blocks within it and retrying the whole query would lead to some of them transactions to be executed twice (which would be a problem if they aren't idempotent).
Since read committed isolation relies on top-level query layer retries for resolving serialization errors, we would require another mechanism to resolve them for multi-statement queries. Implement Pg style "read committed update checking" mechanism for resolving conflicts #11573, that will fix this issue too.
Issue Type
kind/bug
Warning: Please confirm that this issue does not contain any sensitive information
[X] I confirm this issue does not contain any sensitive information.
Jira Link: DB-10735
Description
As part of fixing #21361, query layer retries were blocked for multi-statement queries via simple query protocol since a query could have multiple transaction blocks within it and retrying the whole query would lead to some of them transactions to be executed twice (which would be a problem if they aren't idempotent).
Since read committed isolation relies on top-level query layer retries for resolving serialization errors, we would require another mechanism to resolve them for multi-statement queries. Implement Pg style "read committed update checking" mechanism for resolving conflicts #11573, that will fix this issue too.
Issue Type
kind/bug
Warning: Please confirm that this issue does not contain any sensitive information