Re: Asynchronous execution support for Custom Scan

From: Kazutaka Onishi <onishi(at)heterodb(dot)com>
To: Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com>
Cc: Kohei KaiGai <kaigai(at)heterodb(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Asynchronous execution support for Custom Scan
Date: 2022-09-05 13:32:19
Message-ID: CAJuF6cNjrHkMciNCqSbr4AaBUev5L17ROD7KfLpEzyxHNEwXng@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(dot)fujita(at)gmail(dot)com>:
>
> On Fri, Sep 2, 2022 at 10:43 PM Kazutaka Onishi <onishi(at)heterodb(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2022-09-05 13:40:43 Re: Fix possible bogus array out of bonds (src/backend/access/brin/brin_minmax_multi.c)
Previous Message houzj.fnst@fujitsu.com 2022-09-05 13:04:33 RE: Perform streaming logical transactions by background workers and parallel apply