Re: Inherited UPDATE/DELETE vs async execution - Mailing list pgsql-hackers

From Etsuro Fujita
Subject Re: Inherited UPDATE/DELETE vs async execution
Date
Msg-id CAPmGK15w3iYyEDraiNwuzhEfRLXY-crQgbTS0G_rAp5z9kw9NA@mail.gmail.com
Whole thread Raw
In response to Re: Inherited UPDATE/DELETE vs async execution  (Amit Langote <amitlangote09@gmail.com>)
Responses Re: Inherited UPDATE/DELETE vs async execution
List pgsql-hackers
On Thu, May 13, 2021 at 3:32 PM Amit Langote <amitlangote09@gmail.com> wrote:
> On Wed, May 12, 2021 at 6:45 PM Etsuro Fujita <etsuro.fujita@gmail.com> wrote:
> > Here is a rebased version of the patch.  I'm planning to apply this tommorow.
>
> +   /*
> +    * Finally, unset the async-capable flag if it is set.
> +    */
>
> Would it make sense to expand here even just a bit on why we must do this?

+1  How about something like this?

"Finally, unset the async-capable flag if it is set, as we currently
don't support asynchronous execution of direct modifications."

Best regards,
Etsuro Fujita



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Teaching users how they can get the most out of HOT in Postgres 14
Next
From: David Rowley
Date:
Subject: Re: Executor code - found an instance of a WHILE that should just be an IF