Received: from makus.postgresql.org (makus.postgresql.org [98.129.198.125])
	by mail.postgresql.org (Postfix) with ESMTP id 524C4CBE9C2
	for <pgsql-jdbc@postgresql.org>; Thu, 15 Dec 2011 10:03:05 -0400 (AST)
Received: from mail-ey0-f174.google.com ([209.85.215.174])
	by makus.postgresql.org with esmtp (Exim 4.72)
	(envelope-from <ringerc@ringerc.id.au>) id 1RbBto-00020X-8i
	for pgsql-jdbc@postgresql.org; Thu, 15 Dec 2011 14:03:05 +0000
Received: by eaaj10 with SMTP id j10so1921886eaa.19
	for <pgsql-jdbc@postgresql.org>; Thu, 15 Dec 2011 06:02:51 -0800 (PST)
Received: by 10.204.153.199 with SMTP id l7mr1065961bkw.88.1323957770783;
	Thu, 15 Dec 2011 06:02:50 -0800 (PST)
Received: from ayaki.localdomain (124-169-254-28.dyn.iinet.net.au.
	[124.169.254.28])
	by mx.google.com with ESMTPS id q16sm14545628bky.10.2011.12.15.06.02.46
	(version=SSLv3 cipher=OTHER); Thu, 15 Dec 2011 06:02:49 -0800 (PST)
Message-ID: <4EE9FE03.7070107@ringerc.id.au>
Date: Thu, 15 Dec 2011 22:02:43 +0800
From: Craig Ringer <ringerc@ringerc.id.au>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:7.0.1) Gecko/20110930 Thunderbird/7.0.1
MIME-Version: 1.0
To: =?UTF-8?B?UmFkb3PFgmF3IFNtb2d1cmE=?= <rsmogura@softperience.eu>
CC: David Fetter <david@fetter.org>, Sylvain Mougenot <smougenot@sqli.com>,
	pgsql-jdbc@postgresql.org
Subject: Re: Re: [SQL] JDBC Statement.setQueryTimeout : is there plan
	to implement this?
References: 
 <CACKdPFjK_UsZ5wExD-RvBbvi6Zo-VYtoxQsCUpWXzTN9kywj7w@mail.gmail.com>
	<4EE8AC41.2040505@ringerc.id.au>
	<20111214161349.GA31176@fetter.org>
	<4EE968FF.5010604@ringerc.id.au> <4EE97B85.50909@ringerc.id.au>
	<c138137e3524335c64e646b0e88e7dbc@mail.softperience.eu>
In-Reply-To: <c138137e3524335c64e646b0e88e7dbc@mail.softperience.eu>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Pg-Spam-Score: -1.2 (-)
X-Archive-Number: 201112/61
X-Sequence-Number: 22515

On 12/15/2011 07:29 PM, Radosław Smogura wrote:
> Long, long time ago I've sent implementation with timers, you need to 
> search archive If you need this.

If it was ages ago, you probably used java.util.Timer, right?

java.util.Timer is not suitable for use in a JDBC driver because it 
doesn't do any exception handling on the timer thread, it's subject to 
congestion on the timer thread, and it offers no way for the driver to 
control the timer thread to cleanly shut it down during unload. It's 
unusable in app servers and not really a great idea anywhere that needs 
to be robust and long-running.

--
Craig Ringer