home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!haven.umd.edu!darwin.sura.net!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!ucbvax!HPLWK.HPL.HP.COM!albert
- From: albert@HPLWK.HPL.HP.COM (Joseph Albert)
- Newsgroups: comp.databases
- Subject: distributed transactions
- Message-ID: <9208210244.AA07031@hplwk.hpl.hp.com>
- Date: 21 Aug 92 02:44:47 GMT
- Sender: daemon@ucbvax.BERKELEY.EDU
- Lines: 13
-
- edwards@world.std.com (Jonathan Edwards) writes:
-
- >Distributed transactions have the well-known effect
- >of eroding system autonomy. If one system goes down, it can leave various
- >locks on the other which can not be broken until the system is recovered
- >(unless they are forcibly broken, resulting in possible inconsistent databases
- >requiring manual resolution).
-
- If a non-blocking commit protocol is used, any transaction started at
- a remote site which went down can be aborted, releasing its locks, and
- leaving the database in a transaction-consistent state.
-
- Joseph Albert
-