Re: Asynchronous execution support for Custom Scan - Mailing list pgsql-hackers

From Kohei KaiGai
Subject Re: Asynchronous execution support for Custom Scan
Date
Msg-id CAOP8fzboEcaoJntVGiSfKr399wA3C2pOVx27c8Hux-shkmYhiw@mail.gmail.com
Whole thread Raw
In response to Re: Asynchronous execution support for Custom Scan  (Ronan Dunklau <ronan.dunklau@aiven.io>)
Responses Re: Asynchronous execution support for Custom Scan  (vignesh C <vignesh21@gmail.com>)
List pgsql-hackers
> > 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.

Best regards,

2022年12月1日(木) 22:27 Ronan Dunklau <ronan.dunklau@aiven.io>:
>
> > 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.
>
> Best regards,
>
> --
> Ronan Dunklau
>
>
>
>


--
HeteroDB, Inc / The PG-Strom Project
KaiGai Kohei <kaigai@heterodb.com>



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Error-safe user functions
Next
From: Thomas Munro
Date:
Subject: Using AF_UNIX sockets always for tests on Windows