Re: bogus varno EXPLAIN bug (was Re: Explain analyze gives bogus varno for dblink views) - Mailing list pgsql-bugs

From Tom Lane
Subject Re: bogus varno EXPLAIN bug (was Re: Explain analyze gives bogus varno for dblink views)
Date
Msg-id 10657.1039190171@sss.pgh.pa.us
Whole thread Raw
In response to bogus varno EXPLAIN bug (was Re: Explain analyze gives bogus varno for dblink views)  (Joe Conway <mail@joeconway.com>)
Responses Re: bogus varno EXPLAIN bug (was Re: Explain analyze gives  (Joe Conway <mail@joeconway.com>)
List pgsql-bugs
Joe Conway <mail@joeconway.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

pgsql-bugs by date:

Previous
From: pgsql-bugs@postgresql.org
Date:
Subject: Bug #839: triggers do not execute in right order in procedures
Next
From: Joe Conway
Date:
Subject: Re: bogus varno EXPLAIN bug (was Re: Explain analyze gives