Re: WIP: Upper planner pathification
| От | Robert Haas |
|---|---|
| Тема | Re: WIP: Upper planner pathification |
| Дата | |
| Msg-id | CA+TgmoYPav6FQvfRTHqFLgLvahs0OV8=47trq1ryyUt_RPwD8A@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: WIP: Upper planner pathification (Tom Lane <tgl@sss.pgh.pa.us>) |
| Список | pgsql-hackers |
On Thu, Mar 17, 2016 at 4:22 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote: > Robert Haas <robertmhaas@gmail.com> writes: >> On Thu, Mar 17, 2016 at 2:31 PM, Tom Lane <tgl@sss.pgh.pa.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. OK - sold. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: