| From: | vignesh C <vignesh21(at)gmail(dot)com> |
|---|---|
| To: | Kohei KaiGai <kaigai(at)heterodb(dot)com> |
| Cc: | Ronan Dunklau <ronan(dot)dunklau(at)aiven(dot)io>, Kazutaka Onishi <onishi(at)heterodb(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com> |
| Subject: | Re: Asynchronous execution support for Custom Scan |
| Date: | 2024-01-14 05:51:58 |
| Message-ID: | CALDaNm0upVsUOmv-LOSzD+Zn==zKWrG=TTn7axnqvbe0WGwTkw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, 2 Dec 2022 at 05:05, Kohei KaiGai <kaigai(at)heterodb(dot)com> wrote:
>
> > > IIUC, we already can use ctid in the where clause on the latest
> > > PostgreSQL, can't we?
> >
> > Oh, sorry, I missed the TidRangeScan. My apologies for the noise.
> >
> I made the ctidscan extension when we developed CustomScan API
> towards v9.5 or v9.6, IIRC. It would make sense just an example of
> CustomScan API (e.g, PG-Strom code is too large and complicated
> to learn about this API), however, makes no sense from the standpoint
> of the functionality.
This patch has been moving from one CF to another CF without any
discussion happening. It has been more than one year since any
activity in this thread. I don't see there is much interest in this
patch. I prefer to return this patch in this CF unless someone is
interested in the patch and takes it forward.
Regards,
Vignesh
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2024-01-14 06:32:05 | Re: Escape output of pg_amcheck test |
| Previous Message | vignesh C | 2024-01-14 05:43:43 | Re: logicalrep_worker_launch -- counting/checking the worker limits |