On Mon, Oct 11, 2010 at 16:17, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> "Kevin Grittner" <Kevin.Grittner@wicourts.gov> writes:
>> David Fetter <david@fetter.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.
To be fair to David, it was sent to *both* pgsql-jdbc and
pgsql-hackers. Maybe it was held for moderation on one and arrived out
of order?
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/