Received: from magus.postgresql.org (magus.postgresql.org [87.238.57.229]) by mail.postgresql.org (Postfix) with ESMTP id 3F0801927BC3 for ; Wed, 14 Dec 2011 23:25:50 -0400 (AST) Received: from mail-yx0-f174.google.com ([209.85.213.174]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1Rb1x5-0006IC-KD for pgsql-sql@postgresql.org; Thu, 15 Dec 2011 03:25:49 +0000 Received: by yenm11 with SMTP id m11so1174427yen.19 for ; Wed, 14 Dec 2011 19:25:33 -0800 (PST) Received: by 10.236.83.112 with SMTP id p76mr1699831yhe.118.1323919532992; Wed, 14 Dec 2011 19:25:32 -0800 (PST) Received: from [10.0.0.53] (office1.postnewspapers.com.au. [150.101.171.128]) by mx.google.com with ESMTPS id a7sm6248304ana.5.2011.12.14.19.25.31 (version=SSLv3 cipher=OTHER); Wed, 14 Dec 2011 19:25:32 -0800 (PST) Message-ID: <4EE968A6.7090008@ringerc.id.au> Date: Thu, 15 Dec 2011 11:25:26 +0800 From: Craig Ringer User-Agent: Mozilla/5.0 (X11; Linux i686; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1 MIME-Version: 1.0 To: pgsql-sql@postgresql.org Subject: Re: JDBC Statement.setQueryTimeout : is there plan to implement this? References: <4EE8AC41.2040505@ringerc.id.au> <20111214161349.GA31176@fetter.org> In-Reply-To: <20111214161349.GA31176@fetter.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -1.2 (-) X-Archive-Number: 201112/54 X-Sequence-Number: 36115 Replied on pgsql-jdbc; please follow the discussion there. -- Craig Ringer