Re: Custom Scan APIs (Re: Custom Plan node)
От | Jim Mlodgenski |
---|---|
Тема | Re: Custom Scan APIs (Re: Custom Plan node) |
Дата | |
Msg-id | CAB_5SRcA7FTUKviejS_HGA81cLC2gkh70wE_GsS+GmJdpSiXmg@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Custom Scan APIs (Re: Custom Plan node) (Kohei KaiGai <kaigai@kaigai.gr.jp>) |
Список | pgsql-hackers |
KaiGai
On Tue, Nov 19, 2013 at 9:41 AM, Kohei KaiGai <kaigai@kaigai.gr.jp> wrote:
Thanks for your review.
2013/11/19 Jim Mlodgenski <jimmy76@gmail.com>:> My initial review on this feature:This variable was only used in Assert() macro, so it causes a warning if you
> - The patches apply and build, but it produces a warning:
> ctidscan.c: In function ‘CTidInitCustomScanPlan’:
> ctidscan.c:362:9: warning: unused variable ‘scan_relid’ [-Wunused-variable]
>
don't put --enable-cassert on the configure script.
Anyway, I adjusted the code to check relid of RelOptInfo directly.
The warning is now gone.
> I'd recommend that you split the part1 patch containing the ctidscan contribOK, I split them off. The part-1 is custom-scan API itself, the part-2 is
> into its own patch. It is more than half of the patch and its certainly
> stands on its own. IMO, I think ctidscan fits a very specific use case and
> would be better off being an extension instead of in contrib.
>
ctidscan portion, and the part-3 is remote join on postgres_fdw.
Attached is a patch for the documentation. I think the documentation still needs a little more work, but it is pretty close. I can add some more detail to it once finish adapting the hadoop_fdw to using the custom scan api and have a better understanding of all of the calls.
Thanks,
--
KaiGai Kohei <kaigai@kaigai.gr.jp>
Вложения
В списке pgsql-hackers по дате отправления: