Re: [PATCH] Re: Proposal to Enable/Disable Index using ALTER INDEX - Mailing list pgsql-hackers

From David Rowley
Subject Re: [PATCH] Re: Proposal to Enable/Disable Index using ALTER INDEX
Date
Msg-id CAApHDvpZqn0Gc5+hex91gK5_y+8WA7ont1hzQyCiikwAMRZwCg@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] Re: Proposal to Enable/Disable Index using ALTER INDEX  (Robert Treat <rob@xzilla.net>)
List pgsql-hackers
On Sun, 8 Jun 2025 at 01:35, Robert Treat <rob@xzilla.net> wrote:
>
> On Fri, Jun 6, 2025 at 8:04 PM David Rowley <dgrowleyml@gmail.com> wrote:
> > Can you list your proposed series of steps you'd recommend to a DBA
> > wishing to remove an index, assuming this feature exists in core as
> > you'd like it to?
> >
>
> Well, the series of steps differs depending on the nature of the
> system being managed. If you are running on a single node with normal
> traffic and resources, you just set the GUC to include the index you
> want to be invisible, wait for a few days (maybe no one runs monthly
> reports on this system?), take a quick look at your monitoring/stats
> to make sure things seem copacetic, and then you drop the index and
> reset the GUC.

Thanks for explaining.

What are your thoughts on cached plans? In this scenario, do you
assume that waiting a few days means that connections get reset and
prepared statements will have been replanned? Or do you think cached
plans don't matter in this scenario?

David



pgsql-hackers by date:

Previous
From: Jelte Fennema-Nio
Date:
Subject: Re: Feature: psql - display current search_path in prompt
Next
From: Laurenz Albe
Date:
Subject: Re: Enhancing PostgreSQL Management and Observability in Cloud Environments