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:29:06 +0000 (15:29 +0900)
committer	Michael Paquier <michael@paquier.xyz>
	Thu, 1 Apr 2021 06:29:06 +0000 (15:29 +0900)
commit	dce3d2610dd627f07ded5a289702c43a6d997495
tree	95b36e28cff026a27130f1602e7c295a36ff723d	tree \| snapshot
parent	58960fca4ef1953220e626aa2bce2446da04bfc7	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