]> git.ipfire.org Git - thirdparty/postgresql.git/commit
projects / thirdparty / postgresql.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: f5ee6a7) | 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)
commit28dc2c25c579232dbba98a0ec62476b4091df96e
treea65b89a4742b3d54aa4522516382e61396caddc0tree | snapshot
parentf5ee6a7acc5db0d77f73aa1db531a684179b5478commit | 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 | blame | history
src/backend/access/heap/heapam.c diff | blob | blame | history
src/test/isolation/expected/tuplelock-upgrade-no-deadlock.out [deleted file] blob | blame | history
src/test/isolation/isolation_schedule diff | blob | blame | history
src/test/isolation/specs/tuplelock-upgrade-no-deadlock.spec [deleted file] blob | blame | history
Mirror of https://git.postgresql.org/git/postgresql.git