aboutsummaryrefslogtreecommitdiff
path: root/src
diff options
context:
space:
mode:
authorRobert Haas <rhaas@postgresql.org>2018-01-23 11:20:18 -0500
committerRobert Haas <rhaas@postgresql.org>2018-01-23 11:22:47 -0500
commit28e04155f17cabda7a18aee31d130aa10e25ee86 (patch)
tree65f7eed3841bab208c141d3482adf2cfd94ae8e7 /src
parent2badb5afb89cd569500ef7c3b23c7a9d11718f2f (diff)
downloadpostgresql-28e04155f17cabda7a18aee31d130aa10e25ee86.tar.gz
postgresql-28e04155f17cabda7a18aee31d130aa10e25ee86.zip
Update obsolete sentence in README.parallel.
Since 9.6, heavyweight locking is not an abstract and unhandled concern of the parallel machinery, but rather something to which we have a specific approach.
Diffstat (limited to 'src')
-rw-r--r--src/backend/access/transam/README.parallel6
1 files changed, 3 insertions, 3 deletions
diff --git a/src/backend/access/transam/README.parallel b/src/backend/access/transam/README.parallel
index 32994719e3b..f09a5806345 100644
--- a/src/backend/access/transam/README.parallel
+++ b/src/backend/access/transam/README.parallel
@@ -125,9 +125,9 @@ worker. This includes:
- State related to pending REINDEX operations, which prevents access to
an index that is currently being rebuilt.
-To prevent undetected or unprincipled deadlocks when running in parallel mode,
-this could should eventually handle heavyweight locks in some way. This is
-not implemented yet.
+To prevent unprincipled deadlocks when running in parallel mode, this code
+also arranges for the leader and all workers to participate in group
+locking. See src/backend/storage/lmgr/README for more details.
Transaction Integration
=======================