Postgres Pro
Downloads
Home   >   mailing lists

Re: query_planner() API change - Mailing list pgsql-hackers

From Tom Lane
Subject Re: query_planner() API change
Date
Msg-id 8666.1375707077@sss.pgh.pa.us
Whole thread Raw
In response to Re: query_planner() API change  (Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>)
List pgsql-hackers
Tree view 
Ashutosh Bapat <ashutosh.bapat@enterprisedb.com> writes:
> Can we change the query_planner() to return both the paths (presorted and
> unsorted) irrespective of the cost of presorted path, and let
> grouping_planner() (or any caller of query_planner()) handle which of them
> to pick up?

That's exactly the result this change would have, since all the potential
Paths are attached to the top-level RelOptInfo.
        regards, tom lane

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: query_planner() API change
Next
From: Greg Stark
Date:
Subject: Re: ALTER SYSTEM SET command to change postgresql.conf parameters (RE: Proposal for Allow postgresql.conf values to be changed via SQL [review])