Re: timeout implementation issues

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

From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Jessica Perry Hekman <jphekman@dynamicdiagrams.com>
Cc: Hiroshi Inoue <Inoue@tpf.co.jp>, Tom Lane <tgl@sss.pgh.pa.us>, Jan Wieck <janwieck@yahoo.com>, Barry Lind <barry@xythos.com>, pgsql-hackers@postgresql.org
Date: 2002-04-06T23:16:22Z
Lists: pgsql-hackers
Jessica Perry Hekman wrote:
> On Sat, 6 Apr 2002, Bruce Momjian wrote:
> 
> > > 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.
> 
> One approach might be for the interface to take care of setting the query
> timeout before each query, and just ask the backend to handle timeouts
> per-query. So from the user's perspective, session-level timeouts would
> exist, but the backend would not have to worry about rolling back
> timeouts.

Yes, that would work, but libpq and psql would have trouble doing full
session timeouts.

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