Re: timeout implementation issues - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: timeout implementation issues
Date
Msg-id 200204062217.g36MH1916519@candle.pha.pa.us
Whole thread Raw
In response to Re: timeout implementation issues  ("Hiroshi Inoue" <Inoue@tpf.co.jp>)
Responses Re: timeout implementation issues  (Jessica Perry Hekman <jphekman@dynamicdiagrams.com>)
Re: timeout implementation issues  ("Hiroshi Inoue" <Inoue@tpf.co.jp>)
List pgsql-hackers
Hiroshi Inoue wrote:
> > -----Original Message-----
> > From: Tom Lane
> > 
> > Jan Wieck <janwieck@yahoo.com> writes:
> > >     Could  we  get  out  of  this  by  defining that "timeout" is
> > >     automatically reset at next statement end?
> > 
> > I was hoping to avoid that, because it seems like a wart.  OTOH,
> > it'd be less of a wart than the global changes of semantics that
> > Bruce is proposing :-(
> 
> Probably I'm misunderstanding this thread.
> Why must the query_timeout be reset particularly ?
> What's wrong with simply issueing set query_timeout
> command just before every query ?

You could do that, but we also imagine cases where people would want to
set a timeout for each query in an entire session.

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026
 


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: RFC: Restructuring pg_aggregate
Next
From: Jessica Perry Hekman
Date:
Subject: Re: timeout implementation issues