Re: Custom Scan APIs (Re: Custom Plan node)
Kohei KaiGai <kaigai@kaigai.gr.jp>
From: Kohei KaiGai <kaigai@kaigai.gr.jp>
To: Stephen Frost <sfrost@snowman.net>
Cc: Robert Haas <robertmhaas@gmail.com>, Kouhei Kaigai <kaigai@ak.jp.nec.com>,
Shigeru Hanada <shigeru.hanada@gmail.com>,
Jim Mlodgenski <jimmy76@gmail.com>,
Tom Lane <tgl@sss.pgh.pa.us>, PgHacker <pgsql-hackers@postgresql.org>,
Peter Eisentraut <peter_e@gmx.net>
Date: 2014-03-04T21:34:36Z
Lists: pgsql-hackers
2014-03-05 5:52 GMT+09:00 Stephen Frost <sfrost@snowman.net>: > * Robert Haas (robertmhaas@gmail.com) wrote: >> On Tue, Mar 4, 2014 at 2:34 PM, Stephen Frost <sfrost@snowman.net> wrote: >> > Alright- so do you feel that the simple ctidscan use-case is a >> > sufficient justification and example of how this can be generally >> > useful that we should be adding these hooks to core..? I'm willing to >> > work through the patch and clean it up this weekend if we agree that >> > it's useful and unlikely to immediately be broken by expected changes.. >> >> Yeah, I think it's useful. But based on Tom's concurrently-posted >> review, I think there's probably a good deal of work left here. > > Yeah, it certainly looks like it. > > KaiGai- will you have time to go over and address Tom's concerns..? > Yes, I need to do. Let me take it through the later half of this week and the weekend. So, I'd like to submit revised one by next Monday. Thanks, -- KaiGai Kohei <kaigai@kaigai.gr.jp>
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