| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Kouhei Kaigai <kaigai(at)ak(dot)jp(dot)nec(dot)com>, Petr Jelinek <petr(at)2ndquadrant(dot)com>, David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: WIP: Upper planner pathification |
| Date: | 2016-03-17 20:22:30 |
| Message-ID: | 31938.1458246150@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Thu, Mar 17, 2016 at 2:31 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Also, I don't particularly see a need for a corresponding API for FDWs.
>> If an FDW is going to do anything in this space, it presumably has to
>> build up ForeignPaths for all the steps anyway. So I'd be inclined
>> to leave GetForeignUpperPaths as-is.
> No idea if that is going to be a significant limitation or not.
> Doesn't seem like it should be, but what do I know?
Well, to my mind the GetForeignUpperPaths API is meant to handle the
common case efficiently. An FDW that's not happy with that can always
get into the create_upper_paths_hook instead.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2016-03-17 20:24:46 | Re: WIP: Upper planner pathification |
| Previous Message | Robert Haas | 2016-03-17 20:16:55 | Re: Make primnodes.h gender neutral |