Received: from mail.gmx.net (pop.gmx.net [194.221.183.20]) by hub.org (8.10.1/8.10.1) with SMTP id e64HGsS83472 for ; Tue, 4 Jul 2000 13:16:54 -0400 (EDT) Received: (qmail 20919 invoked by uid 0); 4 Jul 2000 17:16:42 -0000 Received: from dtmd-3e3699da.pool.mediaways.net (HELO gmx.de) (62.54.153.218) by mail.gmx.net with SMTP; 4 Jul 2000 17:16:42 -0000 Message-ID: <39621CE9.22B3DBE8@gmx.de> Date: Tue, 04 Jul 2000 17:20:41 +0000 From: Dirk Koschuetzki Reply-To: dkoschuetzki@gmx.de X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.14 i686) X-Accept-Language: en MIME-Version: 1.0 To: pgsql-interfaces@postgresql.org Subject: Default mode for transaction in postgreSQL and JDBC Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Archive-Number: 200007/23 Hello, I played around with the transaction management in postgreSQL and I found that the JDBC-Driver allways indicates that the transaction isolation level is "serializable". This is hard coded within the source and changing the transaction isolation level with the provided method gives an exception. So far so good. A second look in the postgreSQL source code (V 6.5.3) indicates that the default isolation level is read commited, the documentation states the same and a check with psql confirms this. So, is the transaction isolation level within my (6.5.3) JDBC-Version really serializable? Regards Dirk Ps.: Please CC me, as I'm currently not subscribed to the list. -- Dirk Koschützki dkoschuetzki@medialift.com OpenPGP messages welcome Fingerprint: E0C4 74F1 9E21 8C90 EEA7 A65A 1868 A81D 5622 74C4