According to my tests the 8.2 driver does not actually enforce the "setQueryTimeout" value regardless of which version
ofPostgresql 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
forthe 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-timeconstraints.
--- On Mon, 7/6/09, Jamie D <jackelofnar@gmail.com> wrote:
> From: Jamie D <jackelofnar@gmail.com>
> Subject: [JDBC] setQueryTimeout
> To: pgsql-jdbc@postgresql.org
> Date: Monday, July 6, 2009, 12:55 AM
> Hi,
>
> Is there any plans to implement setQueryTimeout on the 8.4
> JDBC
> driver?
>
> 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@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-jdbc
>
