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

From Kazutaka Onishi
Subject Re: Asynchronous execution support for Custom Scan
Date
Msg-id CAJuF6cNjrHkMciNCqSbr4AaBUev5L17ROD7KfLpEzyxHNEwXng@mail.gmail.com
Whole thread Raw
In response to Re: Asynchronous execution support for Custom Scan  (Etsuro Fujita <etsuro.fujita@gmail.com>)
Responses Re: Asynchronous execution support for Custom Scan
List pgsql-hackers
Fujita-san,

I'm sorry for my error on your name...

>  IIUC, it uses the proposed
> APIs, but actually executes ctidscans *synchronously*, so it does not
> improve performance.  Right?

Exactly.
The actual CustomScan that supports asynchronous execution will
start processing in CustomScanAsyncRequest,
configure to detect completion via file descriptor in
CustomScanAsyncConfigureWait,
and receive the result in CustomScanAsyncNotify.

> So I'll review the proposed patches with it.
Thank you!

2022年9月5日(月) 15:27 Etsuro Fujita <etsuro.fujita@gmail.com>:
>
> On Fri, Sep 2, 2022 at 10:43 PM Kazutaka Onishi <onishi@heterodb.com> wrote:
> > The asynchronous version "ctidscan" plugin is ready.
>
> Thanks for that!
>
> I looked at the extended version quickly.  IIUC, it uses the proposed
> APIs, but actually executes ctidscans *synchronously*, so it does not
> improve performance.  Right?
>
> Anyway, that version seems to be useful for testing that the proposed
> APIs works well.  So I'll review the proposed patches with it.  I'm
> not Fujii-san, though.  :-)
>
> Best regards,
> Etsuro Fujita



pgsql-hackers by date:

Previous
From: "houzj.fnst@fujitsu.com"
Date:
Subject: RE: Perform streaming logical transactions by background workers and parallel apply
Next
From: David Rowley
Date:
Subject: Re: Fix possible bogus array out of bonds (src/backend/access/brin/brin_minmax_multi.c)