Re: BUG #19916: UNION over hash-only and sort-only columns: could not devise a query plan

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: tharakan(at)gmail(dot)com
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19916: UNION over hash-only and sort-only columns: could not devise a query plan
Date: 2026-11-19 20:21:19
Message-ID: 1127885.1795119679@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

PG Bug reporting form <noreply(at)postgresql(dot)org> writes:
> A UNION whose columns can't all be sorted and can't all be hashed fails
> with an internal error:
> ERROR: XX000: could not devise a query plan for the given query
> LOCATION: set_cheapest, pathnode.c:279
> tsvector has a btree opclass but no hash opclass, and aclitem has a
> hash opclass but no btree one, so neither strategy works for the query
> below. Up to 16 this was reported properly, and INTERSECT and EXCEPT
> over the same columns still are, on every branch:

Yeah, we should catch that nicely, even if it's an edge case.
Will fix, thanks for the report.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Daniel Gustafsson 2026-11-19 20:49:44 Re: BUG #19908: pg_upgrade --check crashes instance if running in a different PID Namespace then the old cluster
Previous Message Robert Haas 2026-11-19 17:55:10 Re: BUG #19908: pg_upgrade --check crashes instance if running in a different PID Namespace then the old cluster