| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Shayon Mukherjee <shayonj(at)gmail(dot)com> |
| Cc: | Sami Imseih <samimseih(at)gmail(dot)com>, Robert Treat <rob(at)xzilla(dot)net>, David Rowley <dgrowleyml(at)gmail(dot)com>, jian he <jian(dot)universality(at)gmail(dot)com>, Gurjeet Singh <gurjeet(at)singh(dot)im>, Nathan Bossart <nathandbossart(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: [PATCH] Proposal to Enable/Disable Index using ALTER INDEX |
| Date: | 2025-08-04 04:19:46 |
| Message-ID: | aJA04tG0ZHC3fbSa@paquier.xyz |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Aug 02, 2025 at 03:09:19PM -0400, Shayon Mukherjee wrote:
> Per this plan, this would mean that pg_hint_plan would need to
> support index-level hints, and it’s not a massive / impossible
> task. But it also means that both systems aren't fighting/overriding
> each other or making it difficult for users to understand when
> exactly an index is being used or not. Ultimately, this would also
> mean that `ALTER INDEX INVISIBLE` is a one-way door, and there is
> only one way to control index visibility in core, which makes sense
> to me.
Sami has proposed a patch for pg_hint_plan that goes in the direction
of a DisableIndex hint, which is doable even if it requires some work
inside the extension code like some refactoring:
https://github.com/ossc-db/pg_hint_plan/issues/226
So I cannot say much about this proposal for core, but for
pg_hint_plan I'm looking at adding that for the v18 release of the
module, which is planned for the end of August/beginning of September.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2025-08-04 04:23:26 | Re: Let plan_cache_mode to be a little less strict |
| Previous Message | Ashutosh Bapat | 2025-08-04 04:17:25 | Re: Dropping publication breaks logical replication |