Re: Teaching planner to short-circuit empty UNION/EXCEPT/INTERSECT inputs

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: Alexander Lakhin <exclusion(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Teaching planner to short-circuit empty UNION/EXCEPT/INTERSECT inputs
Date: 2025-11-06 03:35:43
Message-ID: CAApHDvpCpn3ScvGkvyh9mcXCM+zEL2dj39bViFqkwGykkhmFag@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, 5 Nov 2025 at 22:44, David Rowley <dgrowleyml(at)gmail(dot)com> wrote:
>
> On Wed, 5 Nov 2025 at 18:26, David Rowley <dgrowleyml(at)gmail(dot)com> wrote:
> > I'm considering restricting that code Path to where the
> > path->parent->reloptkind != RELOPT_UPPER_REL.
>
> I couldn't think of anything better, so here's a patch to that effect.

I've pushed this.

David

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Etsuro Fujita 2025-11-06 03:39:05 Re: postgres_fdw: Add more test coverage for EvalPlanQual testing
Previous Message John Naylor 2025-11-06 02:59:50 Re: GiST README typos