From: Tom Lane <tgl@sss.pgh.pa.us>
To: postgresql@zr40.nl
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17644: EXPLAIN VERBOSE fails on query with SEARCH BREADTH
 FIRST
In-reply-to: <17644-3bd1f3036d6d7a16@postgresql.org>
References: <17644-3bd1f3036d6d7a16@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Sun, 16 Oct 2022 16:50:14 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2052063.1665962510.1@sss.pgh.pa.us>
Date: Sun, 16 Oct 2022 19:21:50 -0400
Message-ID: <2052064.1665962510@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/2052064.1665962510%40sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.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