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-02-01 17:42:02 |
Message-ID: | CALDaNm1Jek2D2ZELmL4dVjoHV=fUR750mPJYN1wZKmpyXiwp9w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sun, 14 Jan 2024 at 11:21, vignesh C <vignesh21(at)gmail(dot)com> wrote:
>
> 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.
Since the author or no one else showed interest in taking it forward
and the patch had no activity for more than 1 year, I have changed the
status to RWF. Feel free to add a new CF entry when someone is
planning to work on this.
Regards,
Vignesh
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2024-02-01 17:45:26 | Re: Oversight in reparameterize_path_by_child leading to executor crash |
Previous Message | Sergey Dudoladov | 2024-02-01 17:41:55 | Re: Add connection active, idle time to pg_stat_activity |