| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | blo(dot)talkto(at)gmail(dot)com |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
| Subject: | Re: BUG #17061: Impossible to query the fields of the tuple created by SEARCH BREADTH FIRST BY .. SET .. |
| Date: | 2021-06-17 14:50:14 |
| Message-ID: | 972632.1623941414@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
[ screwed up the cc somehow the first time, sorry for the duplicate ]
PG Bug reporting form <noreply(at)postgresql(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2021-06-17 19:49:47 | Re: BUG #16792: silent corruption of GIN index resulting in SELECTs returning non-matching rows |
| Previous Message | Tom Lane | 2021-06-17 14:07:54 | Re: BUG #16792: silent corruption of GIN index resulting in SELECTs returning non-matching rows |