> 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 ---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster
- RE: AW: [HACKERS] timeout on lock feature Mikheev, Vadim
- AW: [HACKERS] timeout on lock feature Zeugswetter Andreas SB
- Re: AW: [HACKERS] timeout on lock feature Tom Lane
- Re: [HACKERS] timeout on lock feature Nathan Myers
- Re: [HACKERS] timeout on lock featurey Bruce Momjian
- Re: [HACKERS] timeout on lock feature Nathan Myers
- Re: [HACKERS] timeout on lock feat... Bruce Momjian
- Re: [HACKERS] timeout on lock... Nathan Myers
- RE: AW: [HACKERS] timeout on lock feature Mikheev, Vadim
- Re: AW: [HACKERS] timeout on lock feature Bruce Momjian
- Re: AW: [HACKERS] timeout on lock featurey Mikheev, Vadim
- Re: AW: [HACKERS] timeout on lock featurey Bruce Momjian
- AW: [HACKERS] timeout on lock feature Zeugswetter Andreas SB