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

From Tom Lane
Subject Re: allowing extensions to control planner behavior
Date
Msg-id 3131957.1724789735@sss.pgh.pa.us
Whole thread Raw
In response to Re: allowing extensions to control planner behavior  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: allowing extensions to control planner behavior
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> I believe the minimum viable product here
> is probably something like:

> - control over scan methods
> - control over index selection
> - control over join methods
> - control over join order

Seems reasonable.  It might be possible to say that our answer
to "control over join order" is to provide a hook that can modify
the "joinlist" before it's passed to make_one_rel.  If you want
to force a particular join order you can rearrange that
list-of-lists-of-range-table-indexes to do so.  The thing this
would not give you is control over which rel is picked as outer
in any given join step.  Not sure how critical that bit is.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Jeff Davis
Date:
Subject: Re: Introduce new multi insert Table AM and improve performance of various SQL commands with it for Heap AM
Next
From: Nathan Bossart
Date:
Subject: Re: Partitioned tables and [un]loggedness