aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/nodeRecursiveunion.c
diff options
context:
space:
mode:
authorMichael Paquier <michael@paquier.xyz>2021-04-01 15:28:56 +0900
committerMichael Paquier <michael@paquier.xyz>2021-04-01 15:28:56 +0900
commita126a9510def33fedcddf6288ae431f8d6f2f85c (patch)
tree6c93eeccdb63c7ccf20d87bd3a3e99a083da1ed7 /src/backend/executor/nodeRecursiveunion.c
parent448e86c3345bb41d3e530ab204b8f59301cdfb36 (diff)
downloadpostgresql-a126a9510def33fedcddf6288ae431f8d6f2f85c.tar.gz
postgresql-a126a9510def33fedcddf6288ae431f8d6f2f85c.zip
doc: Clarify use of ACCESS EXCLUSIVE lock in various sections
Some sections of the documentation used "exclusive lock" to describe that an ACCESS EXCLUSIVE lock is taken during a given operation. This can be confusing to the reader as ACCESS SHARE is allowed with an EXCLUSIVE lock is used, but that would not be the case with what is described on those parts of the documentation. Author: Greg Rychlewski Discussion: https://postgr.es/m/CAKemG7VptD=7fNWckFMsMVZL_zzvgDO6v2yVmQ+ZiBfc_06kCQ@mail.gmail.com Backpatch-through: 9.6
Diffstat (limited to 'src/backend/executor/nodeRecursiveunion.c')
0 files changed, 0 insertions, 0 deletions