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

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Kouhei Kaigai <kaigai(at)ak(dot)jp(dot)nec(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Kohei KaiGai <kaigai(at)kaigai(dot)gr(dot)jp>, PgHacker <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: ctidscan as an example of custom-scan (Re: [v9.5] Custom Plan API)
Date: 2014-12-15 08:14:37
Message-ID: CAB7nPqQju8RbK=Ywqd9wf=TqxurGay8nLVGMdZyEDVH1+98oaQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Dec 15, 2014 at 4:55 PM, Kouhei Kaigai <kaigai(at)ak(dot)jp(dot)nec(dot)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?
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kouhei Kaigai 2014-12-15 08:40:09 Re: ctidscan as an example of custom-scan (Re: [v9.5] Custom Plan API)
Previous Message Michael Paquier 2014-12-15 08:12:10 Re: tracking commit timestamps