Received: from flex.flex.ro (IDENT:root@[193.230.255.4]) by hub.org (8.9.3/8.9.1) with ESMTP id FAA49573 for ; Tue, 27 Apr 1999 05:08:40 -0400 (EDT) (envelope-from teo@flex.ro) Received: from flex.ro (IDENT:teo@teo.flex.ro [193.230.255.3]) by flex.flex.ro (8.9.1/8.9.1) with ESMTP id LAA09865 for ; Tue, 27 Apr 1999 11:08:22 +0300 Sender: teo@flex.flex.ro Message-ID: <37257F9A.46967444@flex.ro> Date: Tue, 27 Apr 1999 09:12:58 +0000 From: Constantin Teodorescu Organization: FLEX Consulting X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.6 i586) X-Accept-Language: en MIME-Version: 1.0 To: PostgreSQL Interfaces Subject: JDBC and waiting for commit on a locked table in 6.4.2 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hello, I'm using JDBC PostgreSQL with 6.4.2 database. I'm using the new code style (conn.setAutoCommit(false)). When the transaction is waiting for another transaction to terminate, is there a way to set a timeout period , let's say a maximum of 30 seconds ? If the lock still persist after 30 seconds the statement.upDate() to fail and to throw a SQLException? Of course, without the classical watchdog thread object. Thanks in advance, (BTW : I tried the same thing on 6.5 beta 1 and my both transactions have committed without problem. Nice work that MVCC. I'm watching daily the development waiting for the big day of 6.5 final) Best regards, -- Constantin Teodorescu FLEX Consulting Braila, ROMANIA