Re: bogus varno EXPLAIN bug (was Re: Explain analyze gives bogus varno for dblink views)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Joe Conway <mail(at)joeconway(dot)com>
Cc: Kris Jurka <books(at)ejurka(dot)com>, Kris Jurka <jurka(at)ejurka(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: bogus varno EXPLAIN bug (was Re: Explain analyze gives bogus varno for dblink views)
Date: 2002-12-06 15:56:11
Message-ID: 10657.1039190171@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Joe Conway <mail(at)joeconway(dot)com> writes:
> I can confirm this both on cvs tip (pulled after noon PST today) and 7.3
> stable branch. It is not related to dblink, but rather the backend. Here's a
> (contrived) script based on Kris's example to trigger it:

Ah, thanks for the simplified test case. This is undoubtedly my fault
... will look into it. It is probably somewhat related to the join
alias problem found yesterday (ie, somebody somewhere is trying to use
the wrong rangetable list to interpret a Var node).

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Joe Conway 2002-12-06 17:54:58 Re: bogus varno EXPLAIN bug (was Re: Explain analyze gives
Previous Message pgsql-bugs 2002-12-06 07:04:39 Bug #839: triggers do not execute in right order in procedures