Re: Dropping index from large, partitioned table - Mailing list pgsql-admin

From Ron Johnson
Subject Re: Dropping index from large, partitioned table
Date
Msg-id CANzqJaBTqzVH=hPTPGfp2LsJZtQ6otc+Th1PFA=kuALbmfTn_A@mail.gmail.com
Whole thread Raw
In response to Dropping index from large, partitioned table  (Matthew Planchard <msplanchard@gmail.com>)
List pgsql-admin
On Tue, Oct 7, 2025 at 5:01 PM Matthew Planchard <msplanchard@gmail.com> wrote:
I have a very active table with around 1,000 partitions. I would like
to drop a GIN index on one of its columns.

Unfortunately, this is a top-level index, and so it seems impossible
to drop the indexes on each partition individually, which means a
'drop index' requires holding an access exclusive lock on the entire
table until the process completes for all children. That process turns
out to be much too slow, since it requires locking one of our most

Too bad there's no ONLY. clause in DROP INDEX.

--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!

pgsql-admin by date:

Previous
From: Amod Kakade
Date:
Subject: Re: Postgresql fedora - gpg key(s) not working/found ....
Next
From: André Verwijs
Date:
Subject: please add pgadmin4 9.8-2.fc43 to pgadmin repo...