| From: | Karel Zak <zakkr(at)zf(dot)jcu(dot)cz> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | "Ross J(dot) Reedstrom" <reedstrm(at)rice(dot)edu>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jan Wieck <janwieck(at)yahoo(dot)com>, Jessica Perry Hekman <jphekman(at)dynamicdiagrams(dot)com>, Barry Lind <barry(at)xythos(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: timeout implementation issues |
| Date: | 2002-04-08 08:22:11 |
| Message-ID: | 20020408102211.A3729@zf.jcu.cz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| 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(at)zf(dot)jcu(dot)cz>
http://home.zf.jcu.cz/~zakkr/
C, PostgreSQL, PHP, WWW, http://docs.linux.cz, http://mape.jcu.cz
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Karel Zak | 2002-04-08 08:29:35 | Re: timeout implementation issues |
| Previous Message | Joe Conway | 2002-04-08 06:06:43 | Re: unknownin/out patch (was [HACKERS] PQescapeBytea is |