Postgres Pro
Downloads
Home   >   mailing lists

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 284c750e-df4f-0917-c6eb-cd206ebce63f@2ndquadrant.com
Whole thread Raw
In response to Re: Heap lock levels for REINDEX INDEX CONCURRENTLY not quite right?  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
Tree view 
On 2019-05-02 22:42, Andres Freund wrote:
> RangeVarGetRelidExtended() can call the callback multiple times, if
> there are any concurrent schema changes. That's why it's unlocking the
> previously locked heap oid.

Ah that explains it then.

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

pgsql-hackers by date:

Previous
From: Laurenz Albe
Date:
Subject: Re: Identity columns should own only one sequence
Next
From: Peter Eisentraut
Date:
Subject: Re: Heap lock levels for REINDEX INDEX CONCURRENTLY not quite right?