Revert "Avoid spurious deadlocks when upgrading a tuple lock"
authorAlvaro Herrera
Mon, 17 Jun 2019 02:24:20 +0000 (22:24 -0400)
committerAlvaro Herrera
Mon, 17 Jun 2019 02:24:20 +0000 (22:24 -0400)
commit93d4484ef80aa4df04f70348fd34d45d2eb85416
tree5fa4a1bdbf78559009579a84cb5a992422396767
parent0e45e52b5165c403174e942a6c6f96cd99d6192c
Revert "Avoid spurious deadlocks when upgrading a tuple lock"

This reverts commits 3da73d6839dc and de87a084c0a5.

This code has some tricky corner cases that I'm not sure are correct and
not properly tested anyway, so I'm reverting the whole thing for next
week's releases (reintroducing the deadlock bug that we set to fix).
I'll try again afterwards.

Discussion: https://postgr.es/m/[email protected]
src/backend/access/heap/README.tuplock
src/backend/access/heap/heapam.c
src/test/isolation/expected/tuplelock-upgrade-no-deadlock.out [deleted file]
src/test/isolation/isolation_schedule
src/test/isolation/specs/tuplelock-upgrade-no-deadlock.spec [deleted file]