Joe Conway <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> 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
Joe Conway <[EMAIL PROTECTED]> 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. T
This behavior is present in 7.3 as well.
On Thu, 5 Dec 2002, Kris Jurka wrote:
> Using the old < 7.3 version of dblink on 7.4devel gives a
> "get_names_for_var: bogus varno 5" error.
>
> Install the deprecated version of dblink by following the directions in
> the dblink.sql file to comment / un
Using the old < 7.3 version of dblink on 7.4devel gives a
"get_names_for_var: bogus varno 5" error.
Install the deprecated version of dblink by following the directions in
the dblink.sql file to comment / uncomment various parts of the script.
DROP TABLE t1;
CREATE TABLE t1 (a int);
DROP TABLE t
