pgsql: doc: Clarify use of ACCESS EXCLUSIVE lock in various sections

Поиск
Список
Период
Сортировка
От Michael Paquier
Тема pgsql: doc: Clarify use of ACCESS EXCLUSIVE lock in various sections
Дата
Msg-id E1lRqqI-0007SI-CM@gemulon.postgresql.org
обсуждение исходный текст
Список 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(-)

В списке pgsql-committers по дате отправления:

Предыдущее
От: Amit Kapila
Дата:
Сообщение: pgsql: Ensure to send a prepare after we detect concurrent abort during
Следующее
От: Peter Eisentraut
Дата:
Сообщение: pgsql: Make extract(timetz) tests a bit more interesting