From: | John Naylor <john(dot)naylor(at)enterprisedb(dot)com> |
---|---|
To: | cyg0810(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #17097: FailedAssertion at initsplan.c |
Date: | 2021-07-09 13:41:45 |
Message-ID: | CAFBsxsHW60-r=JdH4Mh-MtchSkZ38tYcRnivutOhnXH0b1MdCQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
> run the following sql command through client and the PostgreSQL database
> process will crash:
Thanks for the report! Unfortunately, the stack trace was not informative,
because there are no debug symbols. Here's a minimal reproducer, which also
traps an assertion on PG13. I'll bisect and see how far back it goes.
SELECT v1 FROM LATERAL COALESCE (27) v1
WHERE v1 IN (
SELECT 42 as v1
);
TRAP: FailedAssertion("false", File: "prepjointree.c", Line: 2164, PID:
1322)
0 postgres 0x000000010e78ecd4
ExceptionalCondition + 132
1 postgres 0x000000010e589d85
replace_vars_in_jointree + 613
2 postgres 0x000000010e589c94
replace_vars_in_jointree + 372
3 postgres 0x000000010e589c24
replace_vars_in_jointree + 260
4 postgres 0x000000010e589c94
replace_vars_in_jointree + 372
5 postgres 0x000000010e5899e7
perform_pullup_replace_vars + 199
6 postgres 0x000000010e587382
pull_up_subqueries_recurse + 1954
7 postgres 0x000000010e586ea4
pull_up_subqueries_recurse + 708
8 postgres 0x000000010e586e09
pull_up_subqueries_recurse + 553
9 postgres 0x000000010e586b75
pull_up_subqueries + 37
10 postgres 0x000000010e5761ed subquery_planner
+ 573
11 postgres 0x000000010e5759c7 standard_planner
+ 359
12 postgres 0x000000010e65a39f pg_plan_query +
111
13 postgres 0x000000010e65a462 pg_plan_queries
+ 82
14 postgres 0x000000010e65e9d2
exec_simple_query + 1154
--
John Naylor
EDB: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2021-07-09 15:03:52 | Re: BUG #17094: FailedAssertion at planner.c |
Previous Message | John Naylor | 2021-07-09 12:52:57 | Re: problem in app installation |