pg.ddx.io  pgsql-committers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Etsuro Fujita <efujita@postgresql.org>
To: pgsql-committers@lists.postgresql.org
Subject: pgsql: Allow asynchronous execution in more cases.
Date: Wed, 06 Apr 2022 06:52:37 +0000
Message-ID: <E1nbzWu-000Xul-Vt@gemulon.postgresql.org> (raw)

Allow asynchronous execution in more cases.

In commit 27e1f1456, create_append_plan() only allowed the subplan
created from a given subpath to be executed asynchronously when it was
an async-capable ForeignPath.  To extend coverage, this patch handles
cases when the given subpath includes some other Path types as well that
can be omitted in the plan processing, such as a ProjectionPath directly
atop an async-capable ForeignPath, allowing asynchronous execution in
partitioned-scan/partitioned-join queries with non-Var tlist expressions
and more UNION queries.

Andrey Lepikhov and Etsuro Fujita, reviewed by Alexander Pyhalov and
Zhihong Yu.

Discussion: https://postgr.es/m/659c37a8-3e71-0ff2-394c-f04428c76f08%40postgrespro.ru

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/c2bb02bc2e858ba345b8b33f1f3a54628f719d93

Modified Files
--------------
contrib/postgres_fdw/expected/postgres_fdw.out | 170 +++++++++++++++++++++++++
contrib/postgres_fdw/sql/postgres_fdw.sql      |  41 ++++++
src/backend/nodes/copyfuncs.c                  |   1 +
src/backend/nodes/outfuncs.c                   |   1 +
src/backend/nodes/readfuncs.c                  |   1 +
src/backend/optimizer/plan/createplan.c        |  57 +++++++--
src/backend/optimizer/plan/setrefs.c           |  18 ++-
src/include/nodes/plannodes.h                  |  12 ++
src/include/optimizer/planmain.h               |   1 +
9 files changed, 287 insertions(+), 15 deletions(-)



Message-ID: <E1nbzWu-000Xul-Vt@gemulon.postgresql.org>
Permalink:  ../E1nbzWu-000Xul-Vt@gemulon.postgresql.org/
Also on:    postgresql.org/message-id/E1nbzWu-000Xul-Vt@gemulon.postgresql.org

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-committers@postgresql.org
  Cc: efujita@postgresql.org
  Subject: Re: pgsql: Allow asynchronous execution in more cases.
  In-Reply-To: <E1nbzWu-000Xul-Vt@gemulon.postgresql.org>
  References: <E1nbzWu-000Xul-Vt@gemulon.postgresql.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox