Re: Driver Bug
От | Kris Jurka |
---|---|
Тема | Re: Driver Bug |
Дата | |
Msg-id | Pine.BSO.4.64.0701041248510.24201@leary2.csoft.net обсуждение исходный текст |
Ответ на | Driver Bug ("John LH" <johnlh@aquafold.com>) |
Ответы |
Re: Driver Bug
|
Список | 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
В списке pgsql-jdbc по дате отправления: