Re: dblink_get_result issue

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Marc Mamin" <M(dot)Mamin(at)intershop(dot)de>
Cc: pgsql-general(at)postgresql(dot)org, Joe Conway <mail(at)joeconway(dot)com>
Subject: Re: dblink_get_result issue
Date: 2010-11-10 23:54:09
Message-ID: 24545.1289433249@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"Marc Mamin" <M(dot)Mamin(at)intershop(dot)de> writes:
> I'm experimenting with dblink, and have an issue with async. queries
> that do not return result sets.

> (Postgres 8.3.9)

> --youll need your own connect string to repeat:

> select dblink_connect_u('myconn1', 'hostaddr=127.0.0.1 port=5432
> dbname=postgres user=postgres password=x');

> select dblink_send_query('myconn1', 'create temp table bah(s int8);');
> select pg_sleep(.3);

> SELECT * FROM dblink_get_result('myconn1', true ) as x (t text);

> =>
> ********** Error **********
> remote query result rowtype does not match the specified FROM clause
> rowtype

Hmm. I can reproduce this in 8.4 too, but it seems OK in 9.0. The only
one of the 9.0 commits that seems likely to be relevant is
http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=56cbb611ec749ba867a4cfc09c8b7df0f4446620

which looks a bit overcomplex for a back-patch. Joe, any thoughts?

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Daniel Verite 2010-11-11 00:30:10 Re: NOTIFY/LISTEN why is not a callback as notice processing.
Previous Message Tom Lane 2010-11-10 22:20:31 Re: NOTIFY/LISTEN why is not a callback as notice processing.