Re: BUG #18077: PostgreSQL server subprocess crashed by a SELECT statement with WITH clause
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Richard Guo <guofenglinux@gmail.com>
Cc: fuboat@outlook.com, pgsql-bugs@lists.postgresql.org
Date: 2023-09-05T02:04:33Z
Lists: pgsql-bugs
Richard Guo <guofenglinux@gmail.com> writes: > BTW, do you think get_name_for_var_field() has similar problem for > RTE_SUBQUERY case? The RTE_CTE code path in that function crawls up the > namespace stack before recursing into the CTE while the RTE_SUBQUERY > code patch does not, which looks like an oversight. Hmm, seems suspicious ... > I tried to find a > test case to show it's indeed a problem but with no luck. Note that any test case here would be of the form "dump a view or rule definition", not "EXPLAIN". What did you try? regards, tom lane
Commits
-
Track nesting depth correctly when drilling down into RECORD Vars.
- e0e492e5a928 17.0 landed
- d29812c0c6cd 12.17 landed
- c5b7f791dab9 13.13 landed
- ae13f8166dc3 14.10 landed
- a374f6c61681 11.22 landed
- 53630f12d39b 16.1 landed
- 2679a107a152 15.5 landed
-
Fix get_expr_result_type() to find field names for RECORD Consts.
- 8a15b4178c40 12.17 landed
- 59bc0dfe44a6 13.13 landed
- 479b99125dcc 11.22 landed
-
Allow extracting fields from a ROW() expression in more cases.
- ece1154f4c89 11.22 landed
- 2f02d4a2b9cb 12.17 landed