JavaScript is disabled for your browser. Some features of this site may not work without it.
A Note on the Transaction Backout Problem
dc.contributor.author | Krentel, Mark W. | en_US |
dc.date.accessioned | 2007-04-23T17:13:16Z | |
dc.date.available | 2007-04-23T17:13:16Z | |
dc.date.issued | 1986-02 | en_US |
dc.identifier.citation | http://techreports.library.cornell.edu:8081/Dienst/UI/1.0/Display/cul.cs/TR86-737 | en_US |
dc.identifier.uri | https://hdl.handle.net/1813/6577 | |
dc.description.abstract | The transaction backout problem arises in the area of distributed databases. Suppose failures partition a data-redundant distributed database, and each partition continues to function as if it were the entire database. When the database is reconnected, the transactions executed by different partitions may not be serializable, and hence it may be necessary to back out some of the transactions. The transaction backout problem is to remove the smallest set of transactions that will leave the remaining ones serializable. The general problem is NP-complete, and in this paper we show that the special case of a fixed-size database can be solved in polynomial time by dynamic programming. | en_US |
dc.format.extent | 494022 bytes | |
dc.format.extent | 398245 bytes | |
dc.format.mimetype | application/pdf | |
dc.format.mimetype | application/postscript | |
dc.language.iso | en_US | en_US |
dc.publisher | Cornell University | en_US |
dc.subject | computer science | en_US |
dc.subject | technical report | en_US |
dc.title | A Note on the Transaction Backout Problem | en_US |
dc.type | technical report | en_US |