database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-09-02 04:21:28 +03:00
Code Activity

doc: Clarify use of ACCESS EXCLUSIVE lock in various sections

Browse Source 
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
This commit is contained in:
Michael Paquier
2021-04-01 15:28:37 +09:00
parent 4778826532
commit ffd3391ea9
9 changed files with 31 additions and 22 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
doc/src/sgml/ref/drop_index.sgml
View File

@@ -45,9 +45,10 @@ DROP INDEX [ CONCURRENTLY ] [ IF EXISTS ] <replaceable class="parameter">name</r
<para>
Drop the index without locking out concurrent selects, inserts, updates,
and deletes on the index's table. A normal <command>DROP INDEX</command>
acquires an exclusive lock on the table, blocking other accesses until the
index drop can be completed. With this option, the command instead
waits until conflicting transactions have completed.
acquires an <literal>ACCESS EXCLUSIVE</literal> lock on the table,
blocking other accesses until the index drop can be completed. With
this option, the command instead waits until conflicting transactions
have completed.
</para>
<para>
There are several caveats to be aware of when using this option.