| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | John Naylor <john(dot)naylor(at)enterprisedb(dot)com> |
| Cc: | 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 17:39:58 |
| Message-ID: | 2257078.1625852398@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
John Naylor <john(dot)naylor(at)enterprisedb(dot)com> writes:
> If it saves you some time, the assert happens here in
> replace_vars_in_jointree():
> case RTE_JOIN:
> case RTE_CTE:
> case RTE_NAMEDTUPLESTORE:
> case RTE_RESULT:
> /* these shouldn't be marked LATERAL */
> Assert(false);
> break;
> where the plan has RTE_RESULT
Ah. When converting the FUNCTION RTE to a dummy RESULT,
we must clear its lateral flag to avoid making this
logic unhappy. Fixed.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2021-07-09 20:00:01 | BUG #17098: Assert failed on composing an error message when adding a type to an extension being dropped |
| Previous Message | John Naylor | 2021-07-09 16:53:37 | Re: BUG #17097: FailedAssertion at initsplan.c |