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
Branch
------
REL_13_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/876ecfba4d829f6d6c70ac4aa5f05b03269fbd95
Modified Files
--------------
doc/src/sgml/ddl.sgml | 3 ++-
doc/src/sgml/hstore.sgml | 3 ++-
doc/src/sgml/indexam.sgml | 6 ++++--
doc/src/sgml/maintenance.sgml | 6 ++++--
doc/src/sgml/mvcc.sgml | 3 ++-
doc/src/sgml/pgrowlocks.sgml | 4 ++--
doc/src/sgml/ref/drop_index.sgml | 7 ++++---
doc/src/sgml/ref/reindex.sgml | 17 +++++++++--------
doc/src/sgml/ref/vacuum.sgml | 4 ++--
9 files changed, 31 insertions(+), 22 deletions(-)