Postgres Pro
Downloads
Home   >   mailing lists

Re: DROP INDEX docs - explicit lock naming - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: DROP INDEX docs - explicit lock naming
Date
Msg-id YGVo+weN3sxatGsm@paquier.xyz
Whole thread Raw
In response to Re: DROP INDEX docs - explicit lock naming  (Greg Rychlewski <greg.rychlewski@gmail.com>)
Responses Re: DROP INDEX docs - explicit lock naming
List pgsql-hackers
Tree view 
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
Attachment

pgsql-hackers by date:

Previous
From: Jaime Casanova
Date:
Subject: Re: Crash in BRIN minmax-multi indexes
Next
From: Kyotaro Horiguchi
Date:
Subject: Re: Issue with point_ops and NaN