Re: Custom Scan APIs (Re: Custom Plan node) - Mailing list pgsql-hackers

From Kohei KaiGai
Subject Re: Custom Scan APIs (Re: Custom Plan node)
Date
Msg-id CADyhKSV4+u4OA9Vp5sr_aLpuCmGkj3rPi3xq7hNYBsUW6fSoCA@mail.gmail.com
Whole thread Raw
In response to Re: Custom Scan APIs (Re: Custom Plan node)  (Jim Mlodgenski <jimmy76@gmail.com>)
Responses Re: Custom Scan APIs (Re: Custom Plan node)  (Jim Mlodgenski <jimmy76@gmail.com>)
Re: Custom Scan APIs (Re: Custom Plan node)  (Peter Eisentraut <peter_e@gmx.net>)
Re: Custom Scan APIs (Re: Custom Plan node)  (Shigeru Hanada <shigeru.hanada@gmail.com>)
List pgsql-hackers
Thanks for your review.

2013/11/19 Jim Mlodgenski <jimmy76@gmail.com>:
> My initial review on this feature:
> - 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]
>
This variable was only used in Assert() macro, so it causes a warning if you
don't put --enable-cassert on the configure script.
Anyway, I adjusted the code to check relid of RelOptInfo directly.

> I'd recommend that you split the part1 patch containing the ctidscan contrib
> 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.
>
OK, I split them off. The part-1 is custom-scan API itself, the part-2 is
ctidscan portion, and the part-3 is remote join on postgres_fdw.

Thanks,
--
KaiGai Kohei <kaigai@kaigai.gr.jp>

Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: New option for pg_basebackup, to specify a different directory for pg_xlog
Next
From: Fujii Masao
Date:
Subject: Re: Review: pset autocomplete add missing options