From: Tom Lane <tgl@sss.pgh.pa.us>
To: pgsql-committers@lists.postgresql.org
Subject: pgsql: Enable use of Memoize atop an Append that came from UNION ALL.
Date: Thu, 16 Mar 2023 22:13:50 +0000
Message-ID: <E1pcvr3-003sne-Rb@gemulon.postgresql.org> (raw)
Enable use of Memoize atop an Append that came from UNION ALL.
create_append_path() would only apply get_baserel_parampathinfo
when the path is for a partitioned table, but it's also potentially
useful for paths for UNION ALL appendrels. Specifically, that
supports building a Memoize path atop this one.
While we're in the vicinity, delete some dead code in
create_merge_append_plan(): there's no need for it to support
parameterized MergeAppend paths, and it doesn't look like that
is going to change anytime soon. It'll be easy enough to undo
this when/if it becomes useful.
Richard Guo
Discussion: https://postgr.es/m/CAMbWs4_ABSu4PWG2rE1q10tJugEXHWgru3U8dAgkoFvgrb6aEA@mail.gmail.com
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/9bfd2822b3201f6b0de1e87305b11ee3885b36d9
Modified Files
--------------
src/backend/optimizer/plan/createplan.c | 12 ++----------
src/backend/optimizer/util/pathnode.c | 18 ++++++++++--------
src/test/regress/expected/memoize.out | 24 ++++++++++++++++++++++++
src/test/regress/sql/memoize.sql | 8 ++++++++
4 files changed, 44 insertions(+), 18 deletions(-)
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 using the --to and --cc options:
reply via email
To: pgsql-committers@postgresql.org
Cc: tgl@sss.pgh.pa.us, pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Enable use of Memoize atop an Append that came from UNION ALL.
In-Reply-To: <E1pcvr3-003sne-Rb@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