Thanks to visit codestin.com
Credit goes to postgrespro.com

pgsql: Fix table lock levels for REINDEX INDEX CONCURRENTLY - Mailing list pgsql-committers

From Peter Eisentraut
Subject pgsql: Fix table lock levels for REINDEX INDEX CONCURRENTLY
Date
Msg-id [email protected]
Whole thread Raw
List pgsql-committers
Fix table lock levels for REINDEX INDEX CONCURRENTLY

REINDEX CONCURRENTLY locks tables with ShareUpdateExclusiveLock rather
than the ShareLock used by a plain REINDEX.  However,
RangeVarCallbackForReindexIndex() was not updated for that and still
used the ShareLock only.  This would lead to lock upgrades later,
leading to possible deadlocks.

Reported-by: Andres Freund <[email protected]>
Reviewed-by: Andres Freund <[email protected]>
Reviewed-by: Michael Paquier <[email protected]>
Discussion: https://www.postgresql.org/message-id/flat/20190430151735.wi52sxjvxsjvaxxt%40alap3.anarazel.de

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/add85ead4ab969c1e31d64f4476c2335856f4aa9

Modified Files
--------------
src/backend/commands/indexcmds.c | 45 +++++++++++++++++++++++++++++-----------
1 file changed, 33 insertions(+), 12 deletions(-)


pgsql-committers by date:

Previous
From: Thomas Munro
Date:
Subject: pgsql: Probe only 127.0.0.1 when looking for ports on Unix.
Next
From: Oleg Bartunov
Date:
Subject: Re: pgsql: docs: fist draft version of the PG 12 release notes