git.ipfire.org Git - thirdparty/postgresql.git/commit

]> git.ipfire.org Git - thirdparty/postgresql.git/commit

projects / thirdparty / postgresql.git / commit

author	Michael Paquier <michael@paquier.xyz>
	Thu, 1 Apr 2021 06:28:56 +0000 (15:28 +0900)
committer	Michael Paquier <michael@paquier.xyz>
	Thu, 1 Apr 2021 06:28:56 +0000 (15:28 +0900)
commit	a126a9510def33fedcddf6288ae431f8d6f2f85c
tree	6c93eeccdb63c7ccf20d87bd3a3e99a083da1ed7	tree \| snapshot
parent	448e86c3345bb41d3e530ab204b8f59301cdfb36	commit \| diff

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

doc/src/sgml/ddl.sgml		diff \| blob \| blame \| history
doc/src/sgml/hstore.sgml		diff \| blob \| blame \| history
doc/src/sgml/indexam.sgml		diff \| blob \| blame \| history
doc/src/sgml/maintenance.sgml		diff \| blob \| blame \| history
doc/src/sgml/mvcc.sgml		diff \| blob \| blame \| history
doc/src/sgml/pgrowlocks.sgml		diff \| blob \| blame \| history
doc/src/sgml/ref/drop_index.sgml		diff \| blob \| blame \| history
doc/src/sgml/ref/reindex.sgml		diff \| blob \| blame \| history
doc/src/sgml/ref/vacuum.sgml		diff \| blob \| blame \| history

Mirror of https://git.postgresql.org/git/postgresql.git

RSS Atom