Re: BUG #16594: DROP INDEX CONCURRENTLY fails on partitioned table with a non helpful error message. - Mailing list pgsql-bugs

From Michael Paquier
Subject Re: BUG #16594: DROP INDEX CONCURRENTLY fails on partitioned table with a non helpful error message.
Date
Msg-id 20200829013433.GA1529@paquier.xyz
Whole thread Raw
In response to Re: BUG #16594: DROP INDEX CONCURRENTLY fails on partitioned table with a non helpful error message.  (Michael Paquier <michael@paquier.xyz>)
Responses Re: BUG #16594: DROP INDEX CONCURRENTLY fails on partitioned table with a non helpful error message.  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Re: BUG #16594: DROP INDEX CONCURRENTLY fails on partitioned table with a non helpful error message.  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-bugs
On Fri, Aug 28, 2020 at 08:22:42AM +0900, Michael Paquier wrote:
> Yes, adding that to RemoveRelations() makes sense.  Thanks for the
> patch.

I got some room to test the patch, and the place of the check looks
good to me.  I think that I would move the new check before we set
PERFORM_DELETION_CONCURRENTLY for non-temporary relations though, as a
partition tree can be temporary as long as all its members are
temporary.
--
Michael

Attachment

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #16600: Postgres can't upper lower diacritic character of Croatina alfabet
Next
From: Tom Lane
Date:
Subject: Re: [BUG] plpgsql RETURN QUERY with toasted fields -vs- DROP/TRUNCATE