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
both the tests fail, but when we change the tests to use withPreferQueryMode("simple"), they pass.
In the former mode, the object lock calls aren't being issued for the retries.
More details.
For transparent statement retries from ysql, we seem to receive the object lock requests for statements being retried only in simple query execution mode. In extended mode, the object lock requests aren't being made on statement retries. This would cause issues since the object locks could be tied to a transaction that would get aborted on statement retry, and the new transaction would proceed to taking row-level locks without acquiring the required object locks.
Issue Type
kind/bug
Warning: Please confirm that this issue does not contain any sensitive information
I confirm this issue does not contain any sensitive information.
The text was updated successfully, but these errors were encountered:
Jira Link: DB-13996
Description
Once #24596 lands, enable
TEST_enable_object_locking_for_table_locks
, and run the followingboth the tests fail, but when we change the tests to use
withPreferQueryMode("simple")
, they pass.In the former mode, the object lock calls aren't being issued for the retries.
More details.
For transparent statement retries from ysql, we seem to receive the object lock requests for statements being retried only in simple query execution mode. In extended mode, the object lock requests aren't being made on statement retries. This would cause issues since the object locks could be tied to a transaction that would get aborted on statement retry, and the new transaction would proceed to taking row-level locks without acquiring the required object locks.
Issue Type
kind/bug
Warning: Please confirm that this issue does not contain any sensitive information
The text was updated successfully, but these errors were encountered: