| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | pgsql: doc: Clarify use of ACCESS EXCLUSIVE lock in various sections |
| Date: | 2021-04-01 06:30:10 |
| Message-ID: | E1lRqqI-0007SI-CM@gemulon.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
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
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/ffd3391ea94165fbb5adc9534894c62d41138505
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(-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2021-04-01 08:05:11 | pgsql: Make extract(timetz) tests a bit more interesting |
| Previous Message | Amit Kapila | 2021-04-01 02:50:08 | pgsql: Ensure to send a prepare after we detect concurrent abort during |