| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> |
| Cc: | 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 00:11:29 |
| Message-ID: | 200204080011.g380BTl28032@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > > Sorry I couldn't understand your point.
> > > It seems the simplest and the most certain way is to call
> > > 'SET QUERY_TIMEOUT per query. The way dosen't require
> > > RESET at all. Is the overhead an issue ?
> >
> > What about psql and libpq. Doing a timeout before every query is a
> > pain.
>
> Psql and libpq would simply issue the query according to the
> user's request as they currently do. What's pain with it ?
If they wanted to place a timeout on all queries in a session, they
would need a SET for every query, which seems like a pain.
--
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 | Hiroshi Inoue | 2002-04-08 00:27:44 | Re: timeout implementation issues |
| Previous Message | Hiroshi Inoue | 2002-04-07 23:55:58 | Re: timeout implementation issues |