]> granicus.if.org Git - postgresql/commit
projects / postgresql / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 16c4e76) | patch
Revert "Avoid spurious deadlocks when upgrading a tuple lock"
authorAlvaro Herrera <alvherre@alvh.no-ip.org>
Mon, 17 Jun 2019 02:24:21 +0000 (22:24 -0400)
committerAlvaro Herrera <alvherre@alvh.no-ip.org>
Mon, 17 Jun 2019 02:24:21 +0000 (22:24 -0400)
commit9d20b0ec8f2af43041b1a65e5fcd91acc47e9ace
tree19713e1f3369ac4f1b4d7f0097805fba404950c3tree | snapshot
parent16c4e76f1b0a0145572551b7e919b967e406a0b1commit | diff
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/E1hbXKQ-0003g1-0C@gemulon.postgresql.org
src/backend/access/heap/README.tuplock diff | blob | history
src/backend/access/heap/heapam.c diff | blob | history
src/test/isolation/expected/tuplelock-upgrade-no-deadlock.out [deleted file] blob | history
src/test/isolation/isolation_schedule diff | blob | history
src/test/isolation/specs/tuplelock-upgrade-no-deadlock.spec [deleted file] blob | history
Unnamed repository; edit this file 'description' to name the repository.