From: | Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com> |
---|---|
To: | Zhihong Yu <zyu(at)yugabyte(dot)com> |
Cc: | Justin Pryzby <pryzby(at)telsasoft(dot)com>, Alexander Pyhalov <a(dot)pyhalov(at)postgrespro(dot)ru>, "Andrey V(dot) Lepikhov" <a(dot)lepikhov(at)postgrespro(dot)ru>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Defer selection of asynchronous subplans until the executor initialization stage |
Date: | 2022-04-28 06:32:46 |
Message-ID: | CAPmGK17cyoXpOAWkHqEj8qVtE-f-Q8-zOPkkK9dyTuOMQFGDGw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Apr 25, 2022 at 1:29 PM Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com> wrote:
> I modified mark_async_capable_plan() a bit further; 1) adjusted code
> in the ProjectionPath case, just for consistency with other cases, and
> 2) tweaked/improved comments a bit. Attached is a new version of the
> patch (“prevent-async-2.patch”).
>
> As mentioned before, v14 has the same issue, so I created a fix for
> v14, which I’m attaching as well (“prevent-async-2-v14.patch”). In
> the fix I modified is_async_capable_path() the same way as
> mark_async_capable_plan() in HEAD, renaming it to
> is_async_capable_plan(), and updated some comments.
>
> Barring objections, I’ll push/back-patch these.
Done.
Best regards,
Etsuro Fujita
From | Date | Subject | |
---|---|---|---|
Next Message | Yugo NAGATA | 2022-04-28 06:40:11 | Re: Implementing Incremental View Maintenance |
Previous Message | Shinya Kato | 2022-04-28 06:06:30 | Re: Add --{no-,}bypassrls flags to createuser |