| 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-06 22:17:01 |
| Message-ID: | 200204062217.g36MH1916519@candle.pha.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hiroshi Inoue wrote:
> > -----Original Message-----
> > From: Tom Lane
> >
> > Jan Wieck <janwieck(at)yahoo(dot)com> writes:
> > > Could we get out of this by defining that "timeout" is
> > > automatically reset at next statement end?
> >
> > I was hoping to avoid that, because it seems like a wart. OTOH,
> > it'd be less of a wart than the global changes of semantics that
> > Bruce is proposing :-(
>
> 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.
--
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 | Jessica Perry Hekman | 2002-04-06 22:23:00 | Re: timeout implementation issues |
| Previous Message | Tom Lane | 2002-04-06 16:34:52 | Re: RFC: Restructuring pg_aggregate |