Skip site navigation (1) Skip section navigation (2)

Driver Bug

From: "John LH" <johnlh(at)aquafold(dot)com>
To: pgsql-jdbc(at)postgresql(dot)org
Subject: Driver Bug
Date: 2006-12-20 18:22:22
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-jdbc

I've found a bug in the drivers which seem to occur in the "8.1-408 JDBC 3"
and "8.2-504 JDBC 3" drivers when executing on a 8.1 and 8.2 PG Server.  The
problem does not occur on a 8.0 server.

The problem occurs when the following situation is produced ...

1. Connection.autoCommit(true);
2. Statement.setMaxRows(1);
3. Statement.execute("select * from information_schema.parameters");

In this case, the Statement.execute() will never return and basically put
the application in a hanging state.  If the Connection.autoCommit() is set
to false then all works well.  If the Statement.setMaxRows() is set to a
number higher then the number of rows to be returned then all works well.
But if you auto commit is true and max rows is less then the total number of
rows and the statement is executed on PG 8.1 or 8.2.

Any ideas?



pgsql-jdbc by date

Next:From: Kevin MurphyDate: 2006-12-20 19:44:22
Subject: parametrized statements, but always replan?
Previous:From: Morten AndersenDate: 2006-12-20 12:15:56
Subject: Unexpected NullPointerException in "processDeadParsedQueries()" - suggested fix

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group