Skip site navigation (1) Skip section navigation (2)

Re: Implementation of query timeout

From: Radosław Smogura <rsmogura(at)softperience(dot)eu>
To: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: Implementation of query timeout
Date: 2009-10-30 17:35:25
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-jdbc
Dnia piątek 30 październik 2009 o 08:47:02 napisałeś:
> Radoslaw Smogura wrote:
> > I read a TODO list, and I decided to help a bit. So I've tried to
> > implement queryTimeout, currently ony for non-batch statements. You can
> > see code, at
> > and analyze, chceck and test it.
> >
> > Small description how it works.
> >
> > 1. When the query is executed it checks if timeout > 0.
> > 2. If yes it creates TimerTask and add it to the queue, then sends the
> > query to server.
> > 3. On timeout and if statement hasn't ended cancelStatement is called().
> Maybe I am missing something there, but wouldn't it be much easier
> to send the following to the server:
> SET statement_timeout=<n>
> Then all statements that time out throw an exception with SQLSTATE 57014,
> and there's no need for separate threads and canceling the query.
> Yours,
> Lauernz Albe
SET statement_timeout only set timeout for statement processing on server, it 
not include the time of transfering data, which can be long for BLOBs. I've 
found few posts that this is not enaugh solution "SET statement_timeout" from 
above reasons. It's way those timeout is implemented in JDBC side.

Kind regards,
Radek Smogura.

pgsql-jdbc by date

Next:From: Carl ShelbourneDate: 2009-11-03 13:15:21
Subject: Help with prepared statment for crosstab
Previous:From: Albe LaurenzDate: 2009-10-30 07:47:02
Subject: Re: Implementation of query timeout

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group