| From: | peter royal <peter(dot)royal(at)pobox(dot)com> |
|---|---|
| To: | PostgreSQL - JDBC <pgsql-jdbc(at)postgresql(dot)org> |
| Subject: | Re: Implementing setQueryTimeout() - round 2 |
| Date: | 2008-02-19 05:06:00 |
| Message-ID: | 3ACF9DA1-9B0A-4496-A9BE-8C374867ACDE@pobox.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
On Feb 18, 2008, at 8:39 PM, Oliver Jowett wrote:
> Unfortunately statement_timeout is not sufficient for what I need,
> so my changes will end up doing more than that. Here's an attempt at
> a compromise:
>
> Add 4 new connection parameters, associated connection / statement
> values and accessors on the postgresql extension interfaces:
this seems complicated.
can setQueryTimeout set statement_timeout, and then can any additional
logic be implemented externally?
i agree with tom that tying queries actually running long and network
failures isn't appropriate.
-pete
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kris Jurka | 2008-02-19 05:33:08 | Re: JDBC XA Support and Sample code? |
| Previous Message | Oliver Jowett | 2008-02-19 04:39:56 | Re: Implementing setQueryTimeout() - round 2 |