| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Jan Wieck <janwieck(at)yahoo(dot)com> |
| Cc: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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 15:28:42 |
| Message-ID: | 200204081528.g38FSgZ06869@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Jan Wieck wrote:
> > > 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.
>
> Er, how many "applications" have you implemented by simply
> providing a schema and psql?
Actually, I would assume nightly batch jobs are configured this way.
>
> I mean, users normally don't use psql. And if you do, what's
> wrong with controlling the timeout yourself and hitting ^C
> when "you" time out? If you do it in a script, it's
Yes, clearly meaningless for interactive use.
--
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-08 15:29:58 | Re: timeout implementation issues |
| Previous Message | Tom Lane | 2002-04-08 15:08:31 | Re: timeout implementation issues |