Re: [PATCH] Re: Proposal to Enable/Disable Index using ALTER INDEX
David Rowley <dgrowleyml@gmail.com>
From: David Rowley <dgrowleyml@gmail.com>
To: Robert Treat <rob@xzilla.net>
Cc: Sami Imseih <samimseih@gmail.com>, Shayon Mukherjee <shayonj@gmail.com>, jian he <jian.universality@gmail.com>, Gurjeet Singh <gurjeet@singh.im>, Nathan Bossart <nathandbossart@gmail.com>, pgsql-hackers@lists.postgresql.org
Date: 2025-06-08T01:17:06Z
Lists: 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