]> git.ipfire.org Git - thirdparty/postgresql.git/commit
Revert the commits related to allowing page lock to conflict among parallel group...
authorAmit Kapila <akapila@postgresql.org>
Thu, 6 Jul 2023 02:58:27 +0000 (08:28 +0530)
committerAmit Kapila <akapila@postgresql.org>
Thu, 6 Jul 2023 02:58:27 +0000 (08:28 +0530)
commit907d3dd53159fb50402ec292ad60b2452c281310
tree358e8bb62a53a52e191ec5b3c7368092a7b326d9
parentfa96a74a0f76c49ac5a43a16fca8bf705fa98d99
Revert the commits related to allowing page lock to conflict among parallel group members.

This commit reverts the work done by commits 3ba59ccc89 and 72e78d831a.
Those commits were incorrect in asserting that we never acquire any other
heavy-weight lock after acquring page lock other than relation extension
lock. We can acquire a lock on catalogs while doing catalog look up after
acquring page lock.

This won't impact any existing feature but we need to think some other way
to achieve this before parallelizing other write operations or even
improving the parallelism in vacuum (like allowing multiple workers
for an index).

Reported-by: Jaime Casanova
Author: Amit Kapila
Backpatch-through: 13
Discussion: https://postgr.es/m/CAJKUy5jffnRKNvRHKQ0LynRb0RJC-o4P8Ku3x9vGAVLwDBWumQ@mail.gmail.com
src/backend/optimizer/plan/planner.c
src/backend/storage/lmgr/README
src/backend/storage/lmgr/deadlock.c
src/backend/storage/lmgr/lock.c
src/backend/storage/lmgr/proc.c