According to my tests the 8.2 driver does not actually enforce the "setQueryTimeout" value regardless of which version of Postgresql is used on the back-end.
The new "socketTimeout" connection option may be used as a kind of 'global' query time-out as it applies to all queries for the connection. However, it is based on socket time-out yet must be caught as a PSQLException or Exception.
Regardless, "setQueryTimeout" enforcement would really help with some enterprise applications which need to enforce real-time constraints.
--- On Mon, 7/6/09, Jamie D <jackelofnar(at)gmail(dot)com> wrote:
> From: Jamie D <jackelofnar(at)gmail(dot)com>
> Subject: [JDBC] setQueryTimeout
> To: pgsql-jdbc(at)postgresql(dot)org
> Date: Monday, July 6, 2009, 12:55 AM
> Is there any plans to implement setQueryTimeout on the 8.4
> Our application uses this statement and is forcing us to
> use 8.2
> driver with Postgresql 8.4.
> Sent via pgsql-jdbc mailing list (pgsql-jdbc(at)postgresql(dot)org)
> To make changes to your subscription:
pgsql-jdbc by date
|Next:||From: Szabó Tamás||Date: 2009-07-10 15:43:52|
|Subject: calling a stored function which return set of records|
|Previous:||From: Andreas Joseph Krogh||Date: 2009-07-07 01:04:04|
|Subject: Re: Retrieving results from ARRAY and ROW|