Re: timeout implementation issues

Bruce Momjian <pgman@candle.pha.pa.us>

From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Jan Wieck <janwieck@yahoo.com>
Cc: Hiroshi Inoue <Inoue@tpf.co.jp>, Tom Lane <tgl@sss.pgh.pa.us>, Jessica Perry Hekman <jphekman@dynamicdiagrams.com>, Barry Lind <barry@xythos.com>, pgsql-hackers@postgresql.org
Date: 2002-04-08T15:28:42Z
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@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026