Re: cannot drop intarray extension - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: cannot drop intarray extension
Date
Msg-id ZmKXMMX3nEswYbCu@paquier.xyz
Whole thread Raw
In response to Re: cannot drop intarray extension  (jian he <jian.universality@gmail.com>)
Responses Re: cannot drop intarray extension
List pgsql-hackers
On Fri, Jun 07, 2024 at 11:32:14AM +0800, jian he wrote:
> in deleteObjectsInList, under certain conditions trying to sort the to
> be deleted object list
> by just using sort_object_addresses seems to work,
> but it looks like a hack.
> maybe the proper fix would be in findDependentObjects.

@@ -1459,6 +1459,7 @@ RemoveRelations(DropStmt *drop)
[...]
-       performMultipleDeletions(objects, drop->behavior, flags);
+       if (list_length(drop->objects) > 1)
+               sortable = false;

I have not studied the patch in details, but this looks
overcomplicated to me.  All the callers of performMultipleDeletions
pass down sortable as true, while deleteObjectsInList() uses this
argument to avoid the sorting on nested calls.  It seems to me that
this could be simpler.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: PgStat_KindInfo.named_on_disk not required in shared stats
Next
From: Dilip Kumar
Date:
Subject: Re: use CREATE DATABASE STRATEGY = FILE_COPY in pg_upgrade