| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Ed Loehr <ed(at)LoehrTech(dot)com>, dave(at)fastcrypt(dot)com, Matthew Kennedy <mkennedy(at)opushealthcare(dot)com>, PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: implementing query timeout |
| Date: | 2002-07-10 22:50:11 |
| Message-ID: | 200207102250.g6AMoB701218@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
Peter Eisentraut wrote:
> Bruce Momjian writes:
>
> > Here is my first draft of a query timeout SET variable.
>
> Unless it only cancels SELECT statements (which may or may not be a good
> idea), please call it statement_timeout.
Woh, you mean only SELECT is a query? Why is it SQL? Do we not use
'query' to mean any SQL command?
--
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 | Bruce Momjian | 2002-07-10 22:52:28 | Re: implementing query timeout |
| Previous Message | Agent155 Support | 2002-07-10 22:00:03 | workaround for lack of REPLACE() function |