Re: [PATCH] Re: Proposal to Enable/Disable Index using ALTER INDEX
Sami Imseih <samimseih@gmail.com>
From: Sami Imseih <samimseih@gmail.com>
To: Gurjeet Singh <gurjeet@singh.im>
Cc: David Rowley <dgrowleyml@gmail.com>, Shayon Mukherjee <shayonj@gmail.com>, Nathan Bossart <nathandbossart@gmail.com>, pgsql-hackers@lists.postgresql.org
Date: 2025-04-03T02:53:17Z
Lists: pgsql-hackers
> That seems like a very good location for this advice. But the current > set of bullet points are all directed towards "... a general procedure > for determining which indexes to create". I propose that a new paragrph, > not a bullet point, be added towards the end of that section which > addresses the options of steps to take before dropping an index. > Something like the following: > Thoughts? This new feature provides the ability to experiment with indexes to create ( or drop ), so I don't think it deviates from the purpose of this paragraphs. This patch will provide the ability for the user to create an index as initially invisible and a GUC, use_invisible_index if set to TRUE to experiment with the new index to see if it improves performance. So, I think providing this pattern to experiment with a new index will fit nicely as a new bulletpoint. -- Sami Imseih Amazon Web Services (AWS)