Re: Custom Scan APIs (Re: Custom Plan node)
Shigeru Hanada <shigeru.hanada@gmail.com>
From: Shigeru Hanada <shigeru.hanada@gmail.com>
To: KaiGai Kohei <kaigai@ak.jp.nec.com>
Cc: Kohei KaiGai <kaigai@kaigai.gr.jp>, Jim Mlodgenski <jimmy76@gmail.com>,
Robert Haas <robertmhaas@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>,
PgHacker <pgsql-hackers@postgresql.org>, Peter Eisentraut <peter_e@gmx.net>
Date: 2013-12-16T10:15:12Z
Lists: pgsql-hackers
KaiGai-san, 2013/12/16 KaiGai Kohei <kaigai@ak.jp.nec.com>: > (2013/12/16 14:15), Shigeru Hanada wrote: >> (1) ctidscan >> Is session_preload_libraries available to enable the feature, like >> shared_*** and local_***? According to my trial it works fine like >> two similar GUCs. >> > It shall be available; nothing different from the two parameters that > we have supported for long time. Sorry, I missed the new feature to > mention about. Check. >> (2) postgres_fdw >> JOIN push--down is a killer application of Custom Scan Provider >> feature, so I think it's good to mention it in the "Remote Query >> Optimization" section. >> > I added an explanation about remote join execution on the section. > Probably, it help users understand why Custom Scan node is here > instead of Join node. Thanks for your suggestion. Check. I think that these patches are enough considered to mark as "Ready for Committer". Regards, -- Shigeru HANADA
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Support multi-argument UNNEST(), and TABLE() syntax for multiple functions.
- 784e762e886e 9.4.0 cited