Re: BUG #19742: `INTERSECT` under a `UNION ALL` with an empty arm fails with "could not find pathkey item t"

From: shihao zhong <zhong950419(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: feasiblechart(at)gmail(dot)com, David Rowley <dgrowleyml(at)gmail(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19742: `INTERSECT` under a `UNION ALL` with an empty arm fails with "could not find pathkey item t"
Date: 2026-10-05 18:39:59
Message-ID: CAGRkXqTtXhQKxju0gMmMO6SWxFJw7G3viWt6txJhyZiDguYFWg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi Tom,

Thanks for pushing these, and for the credit.

> I'm imagining inventing a new RTEKind, say RTE_SETOP, and building
> one of those for each set operation in the nest.

Yes, I would like to work on that. I will start with the RTE and the
Vars, and leave building the setop tlists at parse time for a
follow-on patch.

I will post the first version in a new thread on hackers.

Thanks,
Shihao

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2026-10-05 18:48:11 Re: BUG #19748: tsvectorrecv accepts duplicate lexemes and position 0 that tsvectorin rejects
Previous Message shihao zhong 2026-10-05 18:38:05 Re: BUG #17545: Incorrect selectivity for IS NOT DISTINCT FROM and NULLs