From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jaime Casanova <jcasanov@systemguards.com.ec>
cc: blo.talkto@gmail.com, pgsql-bugs@lists.postgresql.org,
        Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Subject: Re: BUG #17061: Impossible to query the fields of the tuple created
 by SEARCH BREADTH FIRST BY .. SET ..
In-reply-to: <20210918222017.GA12334@ahch-to>
References: <17061-dd7f4825b7da3a9d@postgresql.org>
 <972632.1623941414@sss.pgh.pa.us> <20210918222017.GA12334@ahch-to>
Comments: In-reply-to Jaime Casanova <jcasanov@systemguards.com.ec>
	message dated "Sat, 18 Sep 2021 17:20:17 -0500"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1550446.1632061226.1@sss.pgh.pa.us>
Date: Sun, 19 Sep 2021 10:20:26 -0400
Message-ID: <1550447.1632061226@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1550447.1632061226%40sss.pgh.pa.us>
Precedence: bulk

Jaime Casanova <jcasanov@systemguards.com.ec> writes:
> Just to add fuel to the fire, I just noted that you cannot create a view
> based on a recursive CTE using this syntax.
> ...
> ERROR:  column "breadth" has pseudo-type record

Yeah, I've run into that too.  There's no time to reconsider the
implementation for v14, but I'd sure like to see this revisited
later.  I'm kind of wondering if, instead of a single RECORD
column, we could add each of the SEARCH columns and the depth
column as a separate resjunk column.  (However, I'm not sure
how to extend that approach to the DEPTH FIRST case, which
wants an array.)

			regards, tom lane