From: | Kris Jurka <books(at)ejurka(dot)com> |
---|---|
To: | John LH <johnlh(at)aquafold(dot)com> |
Cc: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: Driver Bug |
Date: | 2007-01-04 17:52:27 |
Message-ID: | Pine.BSO.4.64.0701041248510.24201@leary2.csoft.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
On Wed, 20 Dec 2006, John LH wrote:
> 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.
I cannot reproduce this on a 8.1.5 database with the 8.2-504 driver using
the attached code. Can you? If so could you send back the results of
it's execution until the point it hangs with the additional connection URL
parameter loglevel=2?
Is it possible you just have a very large amount of data in
information_schema.parameters and it's taking a while to respond?
Kris Jurka
From | Date | Subject | |
---|---|---|---|
Next Message | Ken Johanson | 2007-01-04 17:54:06 | Re: Support for DatabaseMetadata: getCatalogName, getTableName, |
Previous Message | Kris Jurka | 2007-01-04 17:34:02 | Re: ClassCastException DelegatingPreparedStatement |