Re: view + explain + index scan -> bogus varno: 65001 (with some variations) - Mailing list pgsql-bugs

From Jon Nelson
Subject Re: view + explain + index scan -> bogus varno: 65001 (with some variations)
Date
Msg-id CAKuK5J2=ExVj9STLK+Uy+=gFdQir4Ua3qe7Gj-Xecb3=EGhdPQ@mail.gmail.com
Whole thread Raw
In response to Re: view + explain + index scan -> bogus varno: 65001 (with some variations)  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: view + explain + index scan -> bogus varno: 65001 (with some variations)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
On Fri, Jul 1, 2011 at 3:27 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Jon Nelson <jnelson+pgsql@jamponi.net> writes:
>> With 8.4.7, I ran into an issue trying to explain a VIEW query.
>> After much effort, I distilled the query down and was able to
>> replicate the issue with a test script, included below.
>
> FWIW, I can't reproduce such a failure with current 8.4 branch (nor any
> other). =C2=A0It's possible this has been fixed since 8.4.7, but I don't
> immediately see any commit log entries that look related. =C2=A0Another
> possibility is that there's something nondefault about your environment,
> for instance nondefault values for planner cost parameters, and the
> example depends on those to work (or rather, not work).

I managed to reproduce the problem on 9.0.3 as well.
Try adding:

set enable_mergejoin =3D false;

--=20
Jon

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #6088: copy to stdout cannot be stopped with kill(pid) or pg_terminate_backend
Next
From: Tom Lane
Date:
Subject: Re: view + explain + index scan -> bogus varno: 65001 (with some variations)