Re: timeout implementation issues

Hiroshi Inoue wrote:
> > Yes, if you want multiple timeouts, you clearly could go in that
> > direction.  Right now, we are considering only single-statement timing
> > and no one has asked for multiple timers.
> 
> I don't ask multiple timers. ODBC driver would be able
> to handle multiple timeouts without multiple timers in
> my scenario.

I understand.

> > > > but it requires an interface like odbc or jdbc.  It
> > > > is hard to use for libpq or psql.
> > >
> > > We shouldn't expect too much on psql in the first place
> > > because it isn't procedural. I don't expect too much on
> > > libpq either because it's a low level interface. However
> > > applications which use libpq could do like odbc or jdbc
> > > does. Or libpq could also provide a function which encap-
> > > sulates the query timeout handling if necessary.
> > 
> > I certainly would like _something_ that works in psql/libpq,
> 
> Please don't make things complicated by sticking to such
> low level interfaces.

OK, what is your proposal?

--  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,
Pennsylvania19026