| 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-11 10:22:13 |
| Message-ID: | aJnEVcJgGouAlvIO@paquier.xyz |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Aug 04, 2025 at 01:19:46PM +0900, Michael Paquier wrote:
> 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.
FWIW, I have been able to merge the patch to add support for this
DisableIndex hint in pg_hint_plan. So at least this will give people
something to toy with even without this in-core feature. That will be
included in next week's release, available in the version of the
module compatible with v18.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fabrice Chapuis | 2025-08-11 10:27:28 | incremental backup |
| Previous Message | jian he | 2025-08-11 09:53:08 | Re: alter check constraint enforceability |