Re: allowing extensions to control planner behavior - Mailing list pgsql-hackers

From Robert Haas
Subject Re: allowing extensions to control planner behavior
Date
Msg-id CA+TgmoY9NrPp6U+6Px7_Mwmbj4Bph203ON2RGyYYRdcn8JkHJg@mail.gmail.com
Whole thread Raw
In response to Re: allowing extensions to control planner behavior  (Jeff Davis <pgsql@j-davis.com>)
List pgsql-hackers
On Wed, Aug 28, 2024 at 3:23 PM Jeff Davis <pgsql@j-davis.com> wrote:
> On Tue, 2024-08-27 at 15:11 -0400, Robert Haas wrote:
> > - control over scan methods
> > - control over index selection
> > - control over join methods
> > - control over join order
>
> I suggest we split join order into "commutative" and "associative".
>
> The former is both useful and seems relatively easy -- A JOIN B or B
> JOIN A (though there's some nuance about when you try to make that
> decision).
>
> The latter requires controlling an explosion of possibilities, and
> would be an entirely different kind of hook.

My proposal in http://postgr.es/m/CA+TgmoZQyVxnRU--4g2bJonJ8RyJqNi2CHpy-=nwwBTNpAj71A@mail.gmail.com
seems like it can cover both cases.

--
Robert Haas
EDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Jeff Davis
Date:
Subject: Re: allowing extensions to control planner behavior
Next
From: Robert Haas
Date:
Subject: query ID goes missing with extended query protocol