Hi, On Wed, Apr 20, 2022 at 2:04 AM Zhihong Yu <z...@yugabyte.com> wrote: > It is okay to keep the formation in your patch.
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. Thanks! Best regards, Etsuro Fujita
prevent-async-2.patch
Description: Binary data
prevent-async-2-v14.patch
Description: Binary data
