Horton

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

Michael Paquier <michael@paquier.xyz>

View thread View on postgr.es
From: Michael Paquier <michael@paquier.xyz>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: jan.mussler@zalando.de, pgsql-bugs@lists.postgresql.org
Date: 2020-08-27T23:22:42Z
Lists: pgsql-bugs 
On Thu, Aug 27, 2020 at 03:22:18PM -0400, Alvaro Herrera wrote:
> I first tried to add a hack directly in index_drop, but that doesn't
> really work because there's no way to tell whether the partitioned index
> is going to be dropped first or the index partition -- as that code runs
> after the dependency tree has been walked.  The condition has to be
> checked before starting the object-drop code proper.

Yes, adding that to RemoveRelations() makes sense.  Thanks for the
patch.
--
Michael

Commits

  1. Raise error on concurrent drop of partitioned index