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

From: Jon Nelson <jnelson+pgsql(at)jamponi(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: view + explain + index scan -> bogus varno: 65001 (with some variations)
Date: 2011-07-03 03:16:16
Message-ID: CAKuK5J2=ExVj9STLK+Uy+=gFdQir4Ua3qe7Gj-Xecb3=EGhdPQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, Jul 1, 2011 at 3:27 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Jon Nelson <jnelson+pgsql(at)jamponi(dot)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).  It's possible this has been fixed since 8.4.7, but I don't
> immediately see any commit log entries that look related.  Another
> 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 = false;

--
Jon

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2011-07-03 05:40:51 Re: view + explain + index scan -> bogus varno: 65001 (with some variations)
Previous Message Tom Lane 2011-07-03 02:13:23 Re: BUG #6088: copy to stdout cannot be stopped with kill(pid) or pg_terminate_backend