From: | User <user2037(at)ymail(dot)com> |
---|---|
To: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: setQueryTimeout |
Date: | 2009-07-07 14:52:12 |
Message-ID: | 81558.48515.qm@web59810.mail.ac4.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
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
> 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(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-jdbc
>
From | Date | Subject | |
---|---|---|---|
Next Message | Szabó Tamás | 2009-07-10 15:43:52 | calling a stored function which return set of records |
Previous Message | Andreas Joseph Krogh | 2009-07-07 01:04:04 | Re: Retrieving results from ARRAY and ROW |