]> 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:35:27 +0000 (08:05 +0530)
committerAmit Kapila <akapila@postgresql.org>
Thu, 6 Jul 2023 02:35:27 +0000 (08:05 +0530)
commit34f6c606356887d6f5090c92fe7247cbf7946ef0
tree35e3d86defcd865bd76ad6b5d17a70dde6f12285
parent59c2a6fe9b6518255d99a6bbf9006a98a0aefa6b
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