BUG #5094: bad result in dblink_get_result when async command sending

From: "Sergey Tomoulevitch" <phoinix(dot)public(at)gmail(dot)com>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #5094: bad result in dblink_get_result when async command sending
Date: 2009-10-02 07:35:10
Message-ID: 200910020735.n927ZAbM096420@wwwmaster.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


The following bug has been logged online:

Bug reference: 5094
Logged by: Sergey Tomoulevitch
Email address: phoinix(dot)public(at)gmail(dot)com
PostgreSQL version: 8.4
Operating system: any
Description: bad result in dblink_get_result when async command
sending
Details:

Good day!

I find one bug in your function dblink_get_result.
When I send command in async query, eq:

SELECT dblink_send_query('remoteconn', 'INSERT INTO mytable (f1, f2) VALUES
(1,2);');

I can not get result for this, eq:

SELECT dblink_get_result('remoteconn');

I got error "ERRCODE_DATATYPE_MISMATCH".
May be...

if (PQnfields(res) != tupdesc->natts)...

is so bad, because PQnfields(res) - is empty for command?

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Peter Eisentraut 2009-10-02 07:54:53 Re: BUG #5092: to_ascii(); ascii() don't work with bytea
Previous Message Mike Pomraning 2009-10-02 05:05:34 BUG #5093: Prepared query gives different PGresult than exec'd equivalent