|From:||Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>|
|To:||Andreas Seltenreich <seltenreich(at)gmx(dot)de>|
|Subject:||Re: [sqlsmith] subplan variable reference / unassigned NestLoopParams (was: [sqlsmith] Failed assertion in joinrels.c)|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
Andreas Seltenreich <seltenreich(at)gmx(dot)de> writes:
> Tom Lane writes:
>> Well, I certainly think all of these represent bugs:
>>> 3 | ERROR: plan should not reference subplan's variable
>>> 2 | ERROR: failed to assign all NestLoopParams to plan nodes
> These appear to be related. The following query produces the former,
> but if you replace the very last reference of provider with the literal
> 'bar', it raises the latter error.
Fixed that, thanks for the test case!
> ,----[ FWIW: git bisect run ]
> | first bad commit: [e83bb10d6dcf05a666d4ada00d9788c7974ad378]
> | Adjust definition of cheapest_total_path to work better with LATERAL.
There's still something fishy about your git bisect results; they don't
have much to do with what seems to me to be the triggering condition.
I suspect the problem is that git bisect doesn't allow for the possibility
that the symptom might appear and disappear over time, ie it might have
been visible at some early stage of the LATERAL work but been fixed later,
and then reintroduced by still-later optimization efforts.
regards, tom lane
|Next Message||Andrew Dunstan||2015-08-04 19:14:04||Re: upgrade failure from 9.5 to head|
|Previous Message||Alvaro Herrera||2015-08-04 18:28:12||Re: brin index vacuum versus transaction snapshots|