Re: timeout implementation issues
Bruce Momjian <pgman@candle.pha.pa.us>
From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Hiroshi Inoue <Inoue@tpf.co.jp>
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-06T22:17:01Z
Lists: 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, Pennsylvania 19026