pgsql: Teach UNION planner to remove dummy inputs

From: David Rowley <drowley(at)postgresql(dot)org>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Teach UNION planner to remove dummy inputs
Date: 2025-10-04 01:30:48
Message-ID: E1v4r6m-001Lgx-1h@gemulon.postgresql.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Teach UNION planner to remove dummy inputs

This adjusts UNION planning so that the planner produces more optimal
plans when one or more of the UNION's subqueries have been proven to be
empty (a dummy rel).

If any of the inputs are empty, then that input can be removed from the
Append / MergeAppend. Previously, a const-false "Result" node would
appear to represent this. Removing empty inputs has a few extra
benefits when only 1 union child remains as it means the Append or
MergeAppend can be removed in setrefs.c, making the plan slightly faster
to execute. Also, we can provide better n_distinct estimates by looking
at the sole remaining input rel's statistics.

Author: David Rowley <dgrowleyml(at)gmail(dot)com>
Reviewed-by: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Discussion: https://postgr.es/m/CAApHDvri53PPF76c3M94_QNWbJfXjyCnjXuj_2=LYM-0m8WZtw@mail.gmail.com

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/03d40e4b523b2075c198aa89d9445ea8297f8eca

Modified Files
--------------
src/backend/optimizer/prep/prepunion.c | 56 ++++++++++++++++++++++++++++------
src/test/regress/expected/union.out | 51 +++++++++++++++++++++++++++++++
src/test/regress/sql/union.sql | 27 ++++++++++++++++
3 files changed, 125 insertions(+), 9 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Álvaro Herrera 2025-10-05 15:40:47 pgsql: Don't include execnodes.h in brin.h or gin.h
Previous Message David Rowley 2025-10-03 23:19:51 pgsql: Use bms_add_members() instead of bms_union() when possible