Re: BUG #16594: DROP INDEX CONCURRENTLY fails on partitioned table with a non helpful error message.

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: jan(dot)mussler(at)zalando(dot)de, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #16594: DROP INDEX CONCURRENTLY fails on partitioned table with a non helpful error message.
Date: 2020-08-29 01:34:33
Message-ID: 20200829013433.GA1529@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2020-08-29 17:47:19 Re: [BUG] plpgsql RETURN QUERY with toasted fields -vs- DROP/TRUNCATE
Previous Message Tom Lane 2020-08-28 22:07:30 Re: BUG #16600: Postgres can't upper lower diacritic character of Croatina alfabet