Make Append subplans async capable in more cases

From: Alexander Pyhalov <a(dot)pyhalov(at)postgrespro(dot)ru>
To: Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com>
Cc: Alexander Korotkov <aekorotkov(at)gmail(dot)com>, Matheus Alcantara <matheusssilv97(at)gmail(dot)com>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Make Append subplans async capable in more cases
Date: 2026-11-03 13:34:29
Message-ID: 18086964f74852373d993433e7650e82@postgrespro.ru
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

While looking at the latest version of the patch, I've asked myself, why
consider_async_append decisions are a bit different now for Append and
MergeAppend.
Perhaps, Append shouldn't completely avoid introducing async foreign
scans when it deals with range-partitioned tables?

--
Best regards,
Alexander Pyhalov,
Postgres Professional

Attachment Content-Type Size
0001-Make-Append-subplans-async-capable-in-more-cases.patch text/x-diff 4.1 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Etsuro Fujita 2026-11-03 13:35:05 Re: Asynchronous MergeAppend
Previous Message Etsuro Fujita 2026-11-03 13:31:03 Re: Copy-pasto in comment in ExecAppendAsyncReset