Re: [PATCH] Proposal to Enable/Disable Index using ALTER INDEX
| От | Sami Imseih |
|---|---|
| Тема | Re: [PATCH] Proposal to Enable/Disable Index using ALTER INDEX |
| Дата | |
| Msg-id | CAA5RZ0tP=7=0To309a5Qhb7HFeec69g2TN7+d0A1Evsvt+9+fQ@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: [PATCH] Proposal to Enable/Disable Index using ALTER INDEX (David Rowley <dgrowleyml@gmail.com>) |
| Ответы |
Re: Proposal to Enable/Disable Index using ALTER INDEX
Re: [PATCH] Proposal to Enable/Disable Index using ALTER INDEX |
| Список | pgsql-hackers |
My concern with #1 is that when we one day do get query hints, we'll
be left with a bunch of redundant ways to influence planner behaviour.
The GUC is more than just a hint. It can serve as a hint, but it also offers
operational benefits. For example, if I mark an index as invisible and that
only affects a subset of my workload, I don’t need to make the index visible
again. Instead, I can tune that specific workload to operate without it.
Once I’m confident the workload performs well, I can safely drop the index.
I’d argue we should not provide the ALTER option without the GUC, for
more granular control.
Sami
В списке pgsql-hackers по дате отправления: