Re: ctidscan as an example of custom-scan (Re: [v9.5] Custom Plan API) - Mailing list pgsql-hackers

From Kouhei Kaigai
Subject Re: ctidscan as an example of custom-scan (Re: [v9.5] Custom Plan API)
Date
Msg-id 9A28C8860F777E439AA12E8AEA7694F801098F88@BPXM15GP.gisp.nec.co.jp
Whole thread Raw
In response to Re: ctidscan as an example of custom-scan (Re: [v9.5] Custom Plan API)  (Kouhei Kaigai <kaigai@ak.jp.nec.com>)
Responses Re: ctidscan as an example of custom-scan (Re: [v9.5] Custom Plan API)  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
List pgsql-hackers
> > On Mon, Dec 15, 2014 at 4:55 PM, Kouhei Kaigai <kaigai@ak.jp.nec.com>
> wrote:
> > > I'm not certain whether we should have this functionality in contrib
> > > from the perspective of workload that can help, but its major worth
> > > is for an example of custom-scan interface.
> > worker_spi is now in src/test/modules. We may add it there as well, no?
> >
> Hmm, it makes sense for me. Does it also make sense to add a test-case to
> the core regression test cases?
>
The attached patch adds ctidscan module at test/module instead of contrib.
Basic portion is not changed from the previous post, but file locations
and test cases in regression test are changed.

Thanks,
--
NEC OSS Promotion Center / PG-Strom Project
KaiGai Kohei <kaigai@ak.jp.nec.com>

Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Moving RestoreBlockImage from xlogreader.c to xlogutils.c
Next
From: David Rowley
Date:
Subject: Re: Securing "make check" (CVE-2014-0067)