Re: timeout implementation issues

Hiroshi Inoue <inoue@tpf.co.jp>

From: "Hiroshi Inoue" <Inoue@tpf.co.jp>
To: "Bruce Momjian" <pgman@candle.pha.pa.us>
Cc: "Tom Lane" <tgl@sss.pgh.pa.us>, "Jan Wieck" <janwieck@yahoo.com>, "Jessica Perry Hekman" <jphekman@dynamicdiagrams.com>, "Barry Lind" <barry@xythos.com>, <pgsql-hackers@postgresql.org>
Date: 2002-04-08T17:56:08Z
Lists: pgsql-hackers
> -----Original Message-----
> From: Bruce Momjian [mailto:pgman@candle.pha.pa.us]
> 
> Hiroshi Inoue wrote:
> > > I am confused.  Above you state you want SET QUERY_TIMEOUT to be
> > > per-query. I assume you mean that the timeout applies for 
> only the next
> > > query and is turned off after that.
> > 
> > Hmm there seems a misunderstanding between you and I but I
> > don't see what it is. Does *SET QUERY_TIMEOUT* start a timer in
> > your scenario ?  In my scenario *SET QUERY_TIMEOUT* only
> > registers the timeout value for subsequent queries.
> 
> SET QUERY_TIMEOUT does not start a timer.  It makes sure each query
> after the SET is timed and automatically canceled if the single query
> exceeds the timeout interval.

OK using your example, one by one

  	BEGIN WORK;
 	SET query_timeout=20;
 	query fails;
 	SET query_timeout=0;

For what the SET was issued ?
What command is issued if the query was successful ?

 	COMMIT WORK;

regards,
Hiroshi Inoue