]> git.ipfire.org Git - thirdparty/postgresql.git/commit
projects / thirdparty / postgresql.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 609445b) | patch
Revert "Avoid spurious deadlocks when upgrading a tuple lock"
authorAlvaro Herrera <alvherre@alvh.no-ip.org>
Mon, 17 Jun 2019 02:24:20 +0000 (22:24 -0400)
committerAlvaro Herrera <alvherre@alvh.no-ip.org>
Mon, 17 Jun 2019 02:24:20 +0000 (22:24 -0400)
commit03964e58efb8cbb8ecf3f4cdd27c8c757c30e89e
tree755592fdf426499dafe2e3e33566d75011357071tree | snapshot
parent609445b427229fa0fdca470089d802c6f4a62d4dcommit | 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