RE: AW: timeout on lock feature - Mailing list pgsql-hackers

From Mikheev, Vadim
Subject RE: AW: timeout on lock feature
Date
Msg-id 8F4C99C66D04D4118F580090272A7A234D33B7@sectorbase1.sectorbase.com
Whole thread Raw
In response to AW: timeout on lock feature  (Zeugswetter Andreas SB <ZeugswetterA@wien.spardat.at>)
Responses Re: AW: timeout on lock featurey  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
> 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


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [BUG?] tgconstrrelid doesn't survive a dump/restore
Next
From: Bruce Momjian
Date:
Subject: Re: Re: No printable 7.1 docs?