Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Re: BUG #4123: Statement.setQueryTimeout does not work with Postgres Java Driver
- From: Kris Jurka <books(at)ejurka(dot)com>
- To: valgog <valgog(at)gmail(dot)com>
- Cc: pgsql-bugs(at)postgresql(dot)org
- Subject: Re: Re: BUG #4123: Statement.setQueryTimeout does not work with Postgres Java Driver
- Date: Thu, 24 Apr 2008 06:28:18 -0400 (EDT)
- Message-id: <Pine(dot)BSO(dot)4(dot)64(dot)0804240622340(dot)11234(at)leary(dot)csoft(dot)net>
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
- Follow-Ups:
- References:
- Prev by Date: BUG #4126: KRB5/GSSAPI authenication fails for multipart kerberos principals
- Next by Date: Re: HELP pls
- Previous by thread: Re: BUG #4123: Statement.setQueryTimeout does not work with Postgres Java Driver
- Next by thread: Re: BUG #4123: Statement.setQueryTimeout does not work with Postgres Java Driver
- Indexes: