Horton

Re: timeout implementation issues

Bruce Momjian <pgman@candle.pha.pa.us>

View thread
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-07T23:27:52Z
Lists: pgsql-hackers 
> > > 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.
> 
> Sorry I couldn't understand your point.
> It seems the simplest and the most certain way is to call 
> 'SET QUERY_TIMEOUT per query. The way dosen't require
> RESET at all.  Is the overhead an issue ?

What about psql and libpq.  Doing a timeout before every query is a
pain.  I realize it can be done easily in ODBC and JDBC, but we need a
general timeout mechanism.

-- 
  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