| From: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| 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:55:58 |
| Message-ID: | 3CB0DC8E.8B7F0F87@tpf.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian wrote:
>
> > > > 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.
Psql and libpq would simply issue the query according to the
user's request as they currently do. What's pain with it ?
regards,
Hiroshi Inoue
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2002-04-08 00:11:29 | Re: timeout implementation issues |
| Previous Message | Kenny H Klatt | 2002-04-07 23:52:46 | Question on ident authorization |