| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Robert Treat <rob(at)xzilla(dot)net> |
| Cc: | Shayon Mukherjee <shayonj(at)gmail(dot)com>, David Rowley <dgrowleyml(at)gmail(dot)com>, Gurjeet Singh <gurjeet(at)singh(dot)im>, Nathan Bossart <nathandbossart(at)gmail(dot)com>, Sami Imseih <samimseih(at)gmail(dot)com>, jian he <jian(dot)universality(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-09-09 00:10:46 |
| Message-ID: | aL9whuHriv_W6Nfl@paquier.xyz |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Sep 08, 2025 at 09:37:39AM -0400, Robert Treat wrote:
> Thanks for your work on this. For those who may not be aware, Sami did
> implement a version of this in pg_hint_plan{1}, so that is helpful. I think
> it may be worth revisiting this in core, but perhaps once we seen this new
> implementation in action for a bit. (?)
>
> {1}
> https://github.com/ossc-db/pg_hint_plan/commit/d2cfd2f2c1fd18f55123b12c2250a384ccfaefaf
A side note on this one: it may make sense to implement regexp
handling in this new hint, where all the indexes matching the regexp
become ignored by the planner. We have not done that because we
wanted to see the impact of the initial feature first. I don't think
that this would increase the complexity footprint by a lot.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2025-09-09 00:24:03 | Re: PgStat_HashKey padding issue when passed by reference |
| Previous Message | Rishu Bagga | 2025-09-09 00:08:08 | Re: Proposal: Out-of-Order NOTIFY via GUC to Improve LISTEN/NOTIFY Throughput |