| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Jessica Perry Hekman <jphekman(at)dynamicdiagrams(dot)com> |
| Cc: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jan Wieck <janwieck(at)yahoo(dot)com>, Barry Lind <barry(at)xythos(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: timeout implementation issues |
| Date: | 2002-04-06 23:16:22 |
| Message-ID: | 200204062316.g36NGMl20408@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| 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(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-04-07 01:40:14 | Re: timeout implementation issues |
| Previous Message | Peter Eisentraut | 2002-04-06 22:50:01 | Re: RFC: Restructuring pg_aggregate |