| 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-07 23:27:52 |
| Message-ID: | 200204072327.g37NRqR25987@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > > Probably I'm misunderstanding this thread.
> > > Why must the query_timeout be reset particularly ?
> > > 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.
>
> 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. I realize it can be done easily in ODBC and JDBC, but we need a
general timeout mechanism.
--
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-04-07 23:34:02 | Re: timeout implementation issues |
| Previous Message | Joe Conway | 2002-04-07 23:18:57 | unknownin/out patch (was [HACKERS] PQescapeBytea is not multibyte aware) |