| From: | Jessica Perry Hekman <jphekman(at)dynamicdiagrams(dot)com> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| 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 22:23:00 |
| Message-ID: | Pine.LNX.4.21.0204061720540.21428-100000@atalanta.dynamicdiagrams.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
j
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2002-04-06 22:50:01 | Re: RFC: Restructuring pg_aggregate |
| Previous Message | Bruce Momjian | 2002-04-06 22:17:01 | Re: timeout implementation issues |