Probably libpq on windows bug

From: "Filip Hrbek" <filip(dot)hrbek(at)plz(dot)comstar(dot)cz>
To: <pgsql-bugs(at)postgresql(dot)org>
Subject: Probably libpq on windows bug
Date: 2005-02-01 15:24:14
Message-ID: 006e01c50872$167f42a0$1e03a8c0@fhrbek
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hello,

I have a problem with libpq behaviour on Windows.

I have no problem to connect to the database and execute SQL statments. The error happens if I try to call a non-existent SQL function, e.g.

select function_which_is_really_not_here();

I should get an error:
ERROR: function function_which_is_really_not_here() does not exist
HINT: No function matches the given name and argument types. You may need to add explicit type casts.

But I don't - the client does NOTING, it means no error, no result, no hanging...

The problem is in the windows native client (libpq) since this problem does not depend on the database I connect to. On the other hand, if I connect to any database (including the one running on Windows) with other clients (libpq on Linux, jdbc etc.) there is no problem.

Product version: "PostgreSQL 8.0.0 on i686-pc-mingw32, compiled by GCC gcc.exe (GCC) 3.4.2 (mingw-special)"

Best regards
Filip Hrbek

Browse pgsql-bugs by date

  From Date Subject
Next Message Tim Larson 2005-02-01 16:21:28 BUG #1457: ./configure --with-openssl --enabled-thread-safety fails
Previous Message Filip Hrbek 2005-02-01 15:13:56 Password authentication on Windows psql