| 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>, Shigeru Hanada <shigeru(dot)hanada(at)gmail(dot)com>, "pgsql-hackers(at)postgreSQL(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Custom/Foreign-Join-APIs (Re: [v9.5] Custom Plan API) |
| Date: | 2015-03-12 21:28:47 |
| Message-ID: | 305.1426195727@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> I took a look at this patch today and noticed that it incorporates not
> only documentation for the new functionality it adds, but also for the
> custom-scan functionality whose documentation I previously excluded
> from commit on the grounds that it needed more work, especially to
> improve the English. That decision was not popular at the time, and I
> think we need to remedy it before going further with this. I had
> hoped that someone else would care about this work enough to help with
> the documentation, but it seems not, so today I went through the
> documentation in this patch, excluded all of the stuff specific to
> custom joins, and heavily edited the rest. The result is attached.
Looks good; I noticed one trivial typo --- please s/returns/return/ under
ExecCustomScan. Also, perhaps instead of just "set ps_ResultTupleSlot"
that should say "fill ps_ResultTupleSlot with the next tuple in the
current scan direction".
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ewan Higgs | 2015-03-12 22:24:43 | Moving Pivotal's Greenplum work upstream |
| Previous Message | Alvaro Herrera | 2015-03-12 21:20:56 | Re: forward vs backward slashes in msvc build code |