Re: BUG #17097: FailedAssertion at initsplan.c

From: John Naylor <john(dot)naylor(at)enterprisedb(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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 16:53:37
Message-ID: CAFBsxsGKi_+kRMLy5QZk=+D0FJW91tO_UsXkcDfzwoaGYq8XKA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, Jul 9, 2021 at 12:42 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> John Naylor <john(dot)naylor(at)enterprisedb(dot)com> writes:
> > The reproducer I shared stopped working at 7266d0997dd2a (Allow
> > functions-in-FROM to be pulled up if they reduce to constants). I'll dig
> > deeper a bit later unless someone beats me to it.
>
> Sounds like it's my fault then :-(. I'll look closer in a bit.
>
> regards, tom lane

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

--
John Naylor
EDB: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2021-07-09 17:39:58 Re: BUG #17097: FailedAssertion at initsplan.c
Previous Message Tom Lane 2021-07-09 16:42:41 Re: BUG #17097: FailedAssertion at initsplan.c