From: | valgog <valgog(at)gmail(dot)com> |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #4123: Statement.setQueryTimeout does not work with Postgres Java Driver |
Date: | 2008-04-25 16:59:54 |
Message-ID: | e9a628e9-fa81-44a8-a49b-7b9efc235875@s50g2000hsb.googlegroups.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Ok, understood... that could not be so easy anyway :) I supposed that
it should be something, that lays in the JDBC specs...
Regards,
-- Valentine
On Apr 24, 12:28 pm, bo(dot)(dot)(dot)(at)ejurka(dot)com (Kris Jurka) wrote:
> On Wed, 23 Apr 2008, valgog wrote:
> > Is it possible to implement the setStatementTimeout() as somethig
> > like:
>
> > s = c.prepareStatement("SELECT set_config('statement_timeout',
> > <neededTimeoutInMilliseconds>, false);" );
> > s.executeQuery();
> > c.commit();
>
> Not really. This sets a global timeout for all queries while the JDBC API
> specifies that it is per-Statement. Also this only protects against long
> running queries. Recently there was some discussion on the JDBC list
> about soft vs hard timeouts and it seemed the conclusion was that people
> wanted setQueryTimeout to protect against things like the network
> connection dropping that statement_timeout can't do.
>
> In many cases statement_timeout is an adequate substitute for
> setQueryTimeout, but not in the general case that the JDBC driver must
> implement.
>
> Kris Jurka
>
> --
> Sent via pgsql-bugs mailing list (pgsql-b(dot)(dot)(dot)(at)postgresql(dot)org)
> To make changes to your subscription:http://www.postgresql.org/mailpref/pgsql-bugs
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2008-04-25 21:38:08 | Re: BUG #4123: Statement.setQueryTimeout does not work with Postgres Java Driver |
Previous Message | Zdenek Kotala | 2008-04-25 10:06:09 | Re: problem |