| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: query_planner() API change |
| Date: | 2013-08-05 12:51:17 |
| Message-ID: | 8666.1375707077@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2013-08-05 13:51:56 | Re: ALTER SYSTEM SET command to change postgresql.conf parameters (RE: Proposal for Allow postgresql.conf values to be changed via SQL [review]) |
| Previous Message | Tom Lane | 2013-08-05 12:49:44 | Re: query_planner() API change |