> One idea Tom had was to make it only active in a transaction, 
> so you do:
> 
> 	BEGIN WORK;
> 	SET TIMEOUT TO 10;
> 	UPDATE tab SET col = 3;
> 	COMMIT
> 
> Tom is concerned people will do the SET and forget to RESET 
> it, causing all queries to be affected by the timeout.

And what? Queries would be just aborted. It's not critical event
to take responsibility from user.

Vadim

Wed, 18 Apr 2001 12:24:09 -0700
"Mikheev, Vadim" <vmikheev@SECTORBASE.COM>
RE: AW: timeout on lock feature
[ Charset ISO-8859-1 unsupported, converting... ]
> > One idea Tom had was to make it only active in a transaction, 
> > so you do:
> > 
> > 	BEGIN WORK;
> > 	SET TIMEOUT TO 10;
> > 	UPDATE tab SET col = 3;
> > 	COMMIT
> > 
> > Tom is concerned people will do the SET and forget to RESET 
> > it, causing all queries to be affected by the timeout.
> 
> And what? Queries would be just aborted. It's not critical event
> to take responsibility from user.

Hey, I agree.  If the users wants the TIMEOUT, give it to them.

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

Wed, 18 Apr 2001 16:13:28 -0400 (EDT)
Bruce Momjian <pgman@candle.pha.pa.us>
Re: AW: timeout on lock featurey