aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor
diff options
context:
space:
mode:
authorMichael Paquier <michael@paquier.xyz>2021-04-01 15:29:06 +0900
committerMichael Paquier <michael@paquier.xyz>2021-04-01 15:29:06 +0900
commitdce3d2610dd627f07ded5a289702c43a6d997495 (patch)
tree95b36e28cff026a27130f1602e7c295a36ff723d /src/backend/executor
parent58960fca4ef1953220e626aa2bce2446da04bfc7 (diff)
downloadpostgresql-dce3d2610dd627f07ded5a289702c43a6d997495.tar.gz
postgresql-dce3d2610dd627f07ded5a289702c43a6d997495.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')
0 files changed, 0 insertions, 0 deletions