home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.databases
- Path: sparky!uunet!decwrl!world!edwards
- From: edwards@world.std.com (Jonathan Edwards)
- Subject: Re: distributed transactions
- Message-ID: <BtC3E7.9yx@world.std.com>
- Organization: The World Public Access UNIX, Brookline, MA
- References: <9208210244.AA07031@hplwk.hpl.hp.com>
- Date: Fri, 21 Aug 1992 12:44:30 GMT
- Lines: 17
-
- In article <9208210244.AA07031@hplwk.hpl.hp.com> albert@HPLWK.HPL.HP.COM (Joseph Albert) writes:
- >
- >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.
- >
- Could you site some references or examples for this statement?
- Certainly the conventional 2-phase commit protocol (which is what is
- implemented by all commercial instances of distributed TP that I know of)
- can easily leave you in a blocked-or-inconsistent state.
- See Bernstein and Goodman: Concurrency Control and Recovery in Database
- Systems. They state as a 'proposition' that any distributed transaction
- protocol has to be blocking in the presence of communication failures or
- total failures.
-
-
-
-