Skip site navigation (1) Skip section navigation (2)

Re: [JDBC] Support for JDBC setQueryTimeout, et al.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
Cc: "David Fetter" <david(at)fetter(dot)org>, "PG Hackers" <pgsql-hackers(at)postgresql(dot)org>, "PostgreSQL JDBC List" <pgsql-jdbc(at)postgresql(dot)org>
Subject: Re: [JDBC] Support for JDBC setQueryTimeout, et al.
Date: 2010-10-11 14:17:24
Message-ID: 22899.1286806644@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-jdbc
"Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> writes:
> David Fetter <david(at)fetter(dot)org> wrote:
>> Please find enclosed a WIP patch from one of my co-workers
>> intended to support JDBC's setQueryTimeout, along with the patch
>> for JDBC that uses it.
 
> I agree that it would be very nice to support this JDBC feature, but
> I'm not clear on why this can't be done with just JDBC changes using
> the java.util.Timer class and the existing Statement.cancel()
> method.  Can you explain why the backend needed to be touched?

... and, if you are seriously expecting to have that happen, why the
patch was submitted to pgsql-jdbc not pgsql-hackers?  I hadn't even
read it because I assumed it was strictly a JDBC change.

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Magnus HaganderDate: 2010-10-11 14:27:50
Subject: Re: [JDBC] Support for JDBC setQueryTimeout, et al.
Previous:From: Tom LaneDate: 2010-10-11 14:14:27
Subject: Re: On the usefulness of hint bits

pgsql-jdbc by date

Next:From: Magnus HaganderDate: 2010-10-11 14:27:50
Subject: Re: [JDBC] Support for JDBC setQueryTimeout, et al.
Previous:From: Kevin GrittnerDate: 2010-10-11 13:29:16
Subject: Re: [JDBC] Support for JDBC setQueryTimeout, et al.

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group