In article <[email protected]> you wrote:
> How about a poor-man's isolation -- any process other than that
> responsible for the transaction sees a consistent state, never a
> transaction-in-progress. I'm sure there's a name for that.
It is Isolation Level Serializeable. It is the less performant isolation
level and still can generate deadlocks if you have two process doing
transactions.
A more simpler solution would be that process without transactions never see
infligt tx and a second process simple returnes a retry error if touching a
locked ressource.
Bernd
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
