| From: | Michael Banck <mbanck(at)gmx(dot)net> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: allowing extensions to control planner behavior |
| Date: | 2024-08-27 20:08:01 |
| Message-ID: | 66ce3222.050a0220.2f5be0.78ee@mx.google.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On Tue, Aug 27, 2024 at 03:11:15PM -0400, Robert Haas wrote:
> Third, I think there's simply a lack of critical mass in terms of our
> planner hooks. While the ability to add hypothetical indexes has some
> use, the ability to remove indexes from consideration is probably
> significantly more useful.
JFTR, hypopg can also mask away/hide indexes since version 1.4.0:
https://github.com/HypoPG/hypopg/commit/351f14a79daae8ab57339d2367d7f2fc639041f7
I haven't looked closely at the implementation though, and maybe you
meant something else in the above entirely.
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2024-08-27 20:09:10 | Re: Introduce new multi insert Table AM and improve performance of various SQL commands with it for Heap AM |
| Previous Message | Robert Haas | 2024-08-27 20:07:43 | Re: allowing extensions to control planner behavior |