Re: BUG #17061: Impossible to query the fields of the tuple created by SEARCH BREADTH FIRST BY .. SET .. - Mailing list pgsql-bugs

From talk to ben
Subject Re: BUG #17061: Impossible to query the fields of the tuple created by SEARCH BREADTH FIRST BY .. SET ..
Date
Msg-id CAPE8EZ6X17TeALvsA-YFaJesLJYaUY7fseBBnDvqFgNUNQTa8A@mail.gmail.com
Whole thread Raw
In response to Re: BUG #17061: Impossible to query the fields of the tuple created by SEARCH BREADTH FIRST BY .. SET ..  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
On Thu, Jun 17, 2021 at 4:50 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
[ screwed up the cc somehow the first time, sorry for the duplicate ]

PG Bug reporting form <noreply@postgresql.org> writes:
> WITH RECURSIVE mtree(id, name) AS ( ...
> ) SEARCH BREADTH FIRST BY id SET breadth
> SELECT (breadth)."*DEPTH*"
> FROM mtree m;
> ERROR:  CTE m does not have attribute 3

Yeah, I get that with "SELECT (breadth).*" as well.  I'm not entirely sure
what this silly-looking syntax is supposed to mean, but it seems to be
adding an output column named "breadth" to the CTE.  The error is
occurring because said column has not been added to the relevant
CommonTableExpr struct.  Peter?

                        regards, tom lane

Quick update : I checked if BETA2 somehow fixed it, it didn't.

pgsql-bugs by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: BUG #17073: docs - "Improve signal handling reliability"
Next
From: PG Bug reporting form
Date:
Subject: BUG #17079: btree_gin and type coersion combination doesn't work