Re: Heap lock levels for REINDEX INDEX CONCURRENTLY not quite right? - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Heap lock levels for REINDEX INDEX CONCURRENTLY not quite right?
Date
Msg-id 254f0ca0-8e5e-5fdb-dfc7-4cea88f3dc64@2ndquadrant.com
Whole thread Raw
In response to Re: Heap lock levels for REINDEX INDEX CONCURRENTLY not quite right?  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
On 2019-05-07 05:07, Michael Paquier wrote:
> On Sat, May 04, 2019 at 09:59:20PM +0900, Michael Paquier wrote:
>> The result should be no deadlocks happening in the two sessions
>> running the reindex.  I can see the deadlock easily with three psql
>> sessions, running manually the queries.
> 
> +        * If the OID isn't valid, it means the index as concurrently dropped,
> +        * which is not a problem for us; just return normally.
> Typo here s/as/is/.
> 
> I have looked closer at the patch and the change proposed looks good
> to me.

committed

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Inconsistent error message wording for REINDEX CONCURRENTLY
Next
From: Michael Paquier
Date:
Subject: Re: Inconsistent error message wording for REINDEX CONCURRENTLY