| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | postgresql(at)zr40(dot)nl |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #17644: EXPLAIN VERBOSE fails on query with SEARCH BREADTH FIRST |
| Date: | 2022-10-16 23:21:50 |
| Message-ID: | 2052064.1665962510@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
PG Bug reporting form <noreply(at)postgresql(dot)org> writes:
> The following query causes EXPLAIN VERBOSE to raise an error.
> EXPLAIN VERBOSE
> WITH RECURSIVE test AS (
> SELECT 1 AS x
> UNION ALL
> SELECT x+1
> FROM test
> ) SEARCH BREADTH FIRST BY x SET y
> SELECT * FROM test LIMIT 10;
> ERROR: record type has not been registered
Thanks for the report! We'd fixed some closely-related cases during
v14 beta, but nobody stumbled on this one. The key point seems to
be using all constants in the non-recursive term's SELECT list.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2022-10-16 23:43:24 | BUG #17645: Strange queries that stuck in database system |
| Previous Message | Andres Freund | 2022-10-16 21:11:55 | Re: BUG #17641: postgresql service persistently restarts because "could not open shared memory segment" |