The following bug has been logged online:
Bug reference: 1251
Logged by: Fernando Bellas
Email address: fbellas(at)udc(dot)es
PostgreSQL version: 7.4.3
Operating system: Red Hat 7.1
Description: setTransactionIsolation does not seem to work
First of all, the version I am using of PostgreSQL is 7.4.5, and *not* 7.4.3
(I have set 7.4.3 in the form, since it does not allow to choose 7.4.5).
I have tested several JDBC drivers (pg74.213.jdbc3.jar, pg74.215.jdbc3.jar,
pg74.213.jdbc2.jar and pg74.213.jdbc2ee.jar), and
connection.setTransactionIsolation does not change the transaction isolation
level (maybe the problem is with the database and not with the JDBC driver).
The following code prints "2" (TRANSACTION_READ_COMMITED) as the value of
the transaction isolation levels.
int oldTransactionIsolation =
System.out.println("oldTransactionIsolation = " +
System.out.println("newTransactionIsolation = " +
Thanks in advance!
pgsql-bugs by date
|Next:||From: Kris Jurka||Date: 2004-09-13 10:53:49|
|Subject: Re: BUG #1251: setTransactionIsolation does not seem to work|
|Previous:||From: Rafael Martinez Guerrero||Date: 2004-09-13 10:41:09|
|Subject: Re: PosgreSQL is crashing with a signal 11 - Bug?|