From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robert Haas <robertmhaas@gmail.com>
cc: "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Subject: Re: allowing extensions to control planner behavior
In-reply-to: <CA+TgmobN=JiV8uw69aNjSazQm_bpWNGsSCoR18JzpS9b4uhusA@mail.gmail.com>
References: <CA+TgmoZY+baV-T-5ifDn6P=L=aV-VkVBrPmi0TQkcEq-5Finww@mail.gmail.com> <2909615.1724693854@sss.pgh.pa.us> <CA+TgmoZ9PNTKBOeP2rAXoi15nTg+NpYUiSGRgpMhz0nY1wpUtg@mail.gmail.com> <CA+TgmobN=JiV8uw69aNjSazQm_bpWNGsSCoR18JzpS9b4uhusA@mail.gmail.com>
Comments: In-reply-to Robert Haas <robertmhaas@gmail.com>
	message dated "Tue, 27 Aug 2024 11:45:00 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3109293.1724777769.1@sss.pgh.pa.us>
Date: Tue, 27 Aug 2024 12:56:09 -0400
Message-ID: <3109294.1724777769@sss.pgh.pa.us>
Archived-At: <https://www.postgresql.org/message-id/3109294.1724777769%40sss.pgh.pa.us>
Precedence: bulk

Robert Haas <robertmhaas@gmail.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