| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: allowing extensions to control planner behavior |
| Date: | 2024-08-27 16:56:09 |
| Message-ID: | 3109294.1724777769@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> In that vein, here's a new patch set where I've added a second patch
> that allows extensions to control choice of index.
I'm minus-several on this bit, because that is a solved problem and
we really don't need to introduce More Than One Way To Do It. The
intention has always been that get_relation_info_hook can editorialize
on the rel's indexlist by removing entries (or adding fake ones,
in the case of hypothetical-index extensions). For that matter,
if you really want to do it by modifying the IndexInfo rather than
deleting it from the list, that's already possible: just set
indexinfo->hypothetical = true.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2024-08-27 17:17:48 | Re: allowing extensions to control planner behavior |
| Previous Message | Robert Haas | 2024-08-27 16:36:07 | Re: allowing extensions to control planner behavior |