Received: from magus.postgresql.org (magus.postgresql.org [87.238.57.229])
	by mail.postgresql.org (Postfix) with ESMTP id 16AF0EEA158
	for <pgsql-sql@postgresql.org>; Wed, 14 Dec 2011 09:42:35 -0400 (AST)
Received: from mail-qw0-f53.google.com ([209.85.216.53])
	by magus.postgresql.org with esmtp (Exim 4.72)
	(envelope-from <ringerc@ringerc.id.au>) id 1Rap6P-0006S2-Lf
	for pgsql-sql@postgresql.org; Wed, 14 Dec 2011 13:42:34 +0000
Received: by qadb15 with SMTP id b15so529911qad.19
	for <pgsql-sql@postgresql.org>; Wed, 14 Dec 2011 05:42:20 -0800 (PST)
Received: by 10.224.105.11 with SMTP id r11mr9433710qao.68.1323870140730;
	Wed, 14 Dec 2011 05:42:20 -0800 (PST)
Received: from [10.1.1.6] (124-169-254-28.dyn.iinet.net.au. [124.169.254.28])
	by mx.google.com with ESMTPS id j7sm5700189qaq.11.2011.12.14.05.42.18
	(version=SSLv3 cipher=OTHER); Wed, 14 Dec 2011 05:42:19 -0800 (PST)
Message-ID: <4EE8A7B6.7090801@ringerc.id.au>
Date: Wed, 14 Dec 2011 21:42:14 +0800
From: Craig Ringer <ringerc@ringerc.id.au>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
	rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: Sylvain Mougenot <smougenot@sqli.com>
CC: pgsql-sql@postgresql.org
Subject: Re: JDBC Statement.setQueryTimeout : is there plan to implement this?
References: 
 <CACKdPFjK_UsZ5wExD-RvBbvi6Zo-VYtoxQsCUpWXzTN9kywj7w@mail.gmail.com>
In-Reply-To: 
 <CACKdPFjK_UsZ5wExD-RvBbvi6Zo-VYtoxQsCUpWXzTN9kywj7w@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Pg-Spam-Score: -1.2 (-)
X-Archive-Number: 201112/50
X-Sequence-Number: 36111

On 14/12/2011 9:29 PM, Sylvain Mougenot wrote:
> Even if the behaviour is not implemented, I guess it could be "mocked" 
> if the call to Statement.setQueryTimeout(int seconds) generated the 
> select statement "SELECT statement_timeout(SEC)".
> I know this is not ideal but could solve the problem temporarily.
> I could even be turned on by some driver settings.

Please search the mailing list archives for discussion on this topic:

http://www.postgresql.org/search/?m=1&q=setQueryTimeout+&l=&d=-1&s=d 
<http://www.postgresql.org/search/?m=1&q=setQueryTimeout+&l=&d=-1&s=d>

IIRC there are server backend changes required to make it possible to 
implement setQueryTimeout, and nobody's come up with an acceptable 
patch. I haven't followed the issue so I could easily be mistaken, though.
--
Craig Ringer