public inbox for [email protected]  

help / color / mirror / Atom feed

From: Tom Lane <[email protected]>
To: Robert Haas <[email protected]>
Cc: [email protected] <[email protected]>
Subject: Re: allowing extensions to control planner behavior
Date: Tue, 27 Aug 2024 14:24:50 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <CA+TgmoY8sw-xD8EPC-8APd+0KCEdSdREb8bS3wqfpzRqcOmzYg@mail.gmail.com>
References: <CA+TgmoZY+baV-T-5ifDn6P=L=aV-VkVBrPmi0TQkcEq-5Finww@mail.gmail.com>
	<[email protected]>
	<CA+TgmoZ9PNTKBOeP2rAXoi15nTg+NpYUiSGRgpMhz0nY1wpUtg@mail.gmail.com>
	<CA+TgmobN=JiV8uw69aNjSazQm_bpWNGsSCoR18JzpS9b4uhusA@mail.gmail.com>
	<[email protected]>
	<CA+TgmoY8sw-xD8EPC-8APd+0KCEdSdREb8bS3wqfpzRqcOmzYg@mail.gmail.com>

Robert Haas <[email protected]> writes:
> Well, now I'm confused. Just yesterday, in response to the 0001 patch
> that allows extensions to exert control over the join strategy, you
> complained that "Or, if your problem is that the planner wants to scan
> index A but you want it to scan index B, enable_indexscan won't help."

I was just using that to illustrate that making the enable_XXX GUCs
relation-local covers only a small part of the planner-control problem.
You had not, at that point, been very clear that you intended that
patch as only a small part of a solution.

I do think that index selection is pretty well under control already,
thanks to stuff that we put in ages ago at the urging of people who
wanted to write "index advisor" extensions.  (The fact that that
area seems a bit moribund is disheartening, though.  Is it a lack
of documentation?)

			regards, tom lane

view thread (6+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected]
  Subject: Re: allowing extensions to control planner behavior
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox