Horton

Re: timeout implementation issues

Karel Zak <zakkr@zf.jcu.cz>

View thread
From: Karel Zak <zakkr@zf.jcu.cz>
To: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: "Ross J. Reedstrom" <reedstrm@rice.edu>, 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-08T08:22:11Z
Lists: pgsql-hackers 
On Fri, Apr 05, 2002 at 08:32:47PM -0500, Bruce Momjian wrote:
> > Or, as I suggested above, extend the SELECT (and other querys?) syntax
> > seems reasonable. More so than the non-standard 'use this index, really'
> > types of extensions that other RDBMSs provide, that we've rightly avoided.
> 
> I think we need timeout for all statement.

 The Oracle has:

 CREATE PROFILE statement with for example following options:

    CONNECT_TIME
    IDLE_TIME


 I think system resource control per user is more useful than simple
 SET command. There is no problem add other limits like QUERY_TIMEOUT.
    
        Karel

-- 
 Karel Zak  <zakkr@zf.jcu.cz>
 http://home.zf.jcu.cz/~zakkr/
 
 C, PostgreSQL, PHP, WWW, http://docs.linux.cz, http://mape.jcu.cz