Re: allowing extensions to control planner behavior

From: Jeff Davis <pgsql(at)j-davis(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: allowing extensions to control planner behavior
Date: 2024-08-28 19:23:52
Message-ID: 45e381854544d8125d097c334d0fbf3fbdc7014c.camel@j-davis.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

Regards,
Jeff Davis

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2024-08-28 20:12:47 Re: allowing extensions to control planner behavior
Previous Message Robert Haas 2024-08-28 19:15:02 Re: Little cleanup of ShmemInit function names