Is it possible than two simple updates on same table interlocks (deadlock)?
-
12-03-2021 - |
Question
Table A is:
id integer
version varchar
data jsonb (large data 1mb)
fkToBid integer (references B.id constraint)
Table B is:
id integer
other...
Processes are aggressively running the two updates below, in any order and outside any transaction. Updated records on table A refers sometimes to the same record on table B. Also, sometimes the same A records is updated.
UPDATE A.version WHERE A.id=:id
and
UPDATE A.data WHERE A.id=:id
Why/Does this can interlock because updated records in table A refers to the same row in table B? Can this interlock for another reason?
Why do I see an AccessShareLock on the B pk index for these update requests?
No correct solution
Licensed under: CC-BY-SA with attribution
Not affiliated with dba.stackexchange