Horton

Re: DROP INDEX docs - explicit lock naming

Michael Paquier <michael@paquier.xyz>

View thread View on postgr.es
From: Michael Paquier <michael@paquier.xyz>
To: Greg Rychlewski <greg.rychlewski@gmail.com>
Cc: pgsql-hackers@lists.postgresql.org
Date: 2021-04-01T06:32:27Z
Lists: pgsql-hackers 
On Tue, Mar 30, 2021 at 11:29:17PM -0400, Greg Rychlewski wrote:
> Thanks for pointing that out. I've attached a new patch with several other
> updates where I felt confident the docs were referring to an ACCESS
> EXCLUSIVE lock.

Thanks, applied!  I have reviewed the whole and there is one place in
vacuum.sgml that could switch "exclusive lock" to "SHARE UPDATE
EXCLUSIVE lock" but I have left that out as it does not bring more
clarity in the text.  The change in indexam.sgml was partially wrong
as REINDEX CONCURRENTLY does not take an access exclusive lock, and I
have tweaked a bit the wording of pgrowlocks.sgml.
--
Michael

Commits

  1. doc: Clarify use of ACCESS EXCLUSIVE lock in various sections