| From: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> |
|---|---|
| To: | Eric Ridge <eebbrr(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Example Custom Scan Provider Implementation? |
| Date: | 2017-03-08 01:39:01 |
| Message-ID: | 01b95777-88d8-49eb-bd9e-9a3ab202a9b4@lab.ntt.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2017/03/08 7:10, Eric Ridge wrote:
> Hi all!
>
> Does anyone know of a simple, example Custom Scan Provider implementation
> for 9.6+?
>
> I found pg_strom by searching GitHub. Its gpuscan.c looks like maybe it
> implements a pattern similar to what I want to do, but there's a lot of
> extraneous (to me) stuff to parse through.
>
> I'm kinda surprised there isn't an example in contrib/, actually.
Here you go: https://github.com/kaigai/ctidscan
This was proposed originally [1] to go into contrib/, but that didn't
happen somehow.
Thanks,
Amit
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Langote | 2017-03-08 01:55:57 | Re: WARNING: relcache reference leak: relation "p1" not closed |
| Previous Message | Tom Lane | 2017-03-08 00:29:40 | Re: Avoiding OOM in a hash join with many duplicate inner keys |