Re: CustomScan in a larger structure (RE: CustomScan support on readfuncs.c)
От | Kouhei Kaigai |
---|---|
Тема | Re: CustomScan in a larger structure (RE: CustomScan support on readfuncs.c) |
Дата | |
Msg-id | 9A28C8860F777E439AA12E8AEA7694F8011AE6B3@BPXM15GP.gisp.nec.co.jp обсуждение исходный текст |
Ответ на | Re: CustomScan in a larger structure (RE: CustomScan support on readfuncs.c) (Robert Haas <robertmhaas@gmail.com>) |
Ответы |
Re: CustomScan in a larger structure (RE: CustomScan
support on readfuncs.c)
|
Список | pgsql-hackers |
> -----Original Message----- > From: pgsql-hackers-owner@postgresql.org > [mailto:pgsql-hackers-owner@postgresql.org] On Behalf Of Robert Haas > Sent: Thursday, February 11, 2016 1:26 PM > To: Kaigai Kouhei(海外 浩平) > Cc: Andres Freund; Amit Kapila; pgsql-hackers > Subject: Re: CustomScan in a larger structure (RE: [HACKERS] CustomScan support > on readfuncs.c) > > On Wed, Feb 10, 2016 at 1:25 AM, Kouhei Kaigai <kaigai@ak.jp.nec.com> wrote: > > It is pretty good! > > > > The attached patch (primary one) implements the above idea. > > > > Now ExtensibleNode works as a basis structure of data container, > > regardless of CustomScan and ForeignScan. > > Also, fdw_private and custom_private are de-defined to Node * type > > from List * type. It affected to a few FDW APIs. > > I extracted the subset of this that just creates the extensible node > framework and did some cleanup - the result is attached. I will > commit this if nobody objects. > I have no objection of course. > I think the part about whacking around the FDW API is a little more > potentially objectionable to others, so I want to hold off doing that > unless a few more people chime in with +1. Perhaps we could start a > new thread to talk about that specific idea. This is useful even > without that, though. > Thanks, -- NEC Business Creation Division / PG-Strom Project KaiGai Kohei <kaigai@ak.jp.nec.com>
В списке pgsql-hackers по дате отправления: