A note on the transaction backout problem (Q1107967)
From MaRDI portal
| This is the item page for this Wikibase entity, intended for internal use and editing purposes. Please use this page instead for the normal view: A note on the transaction backout problem |
scientific article; zbMATH DE number 4066300
| Language | Label | Description | Also known as |
|---|---|---|---|
| English | A note on the transaction backout problem |
scientific article; zbMATH DE number 4066300 |
Statements
A note on the transaction backout problem (English)
0 references
1987
0 references
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 network is reconnected, the transactions executed by different partitions may not be serializable, and hence it may be necessary to backout 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 and two partitions can be solved in polynomial time by dynamic programming.
0 references
fault-tolerance
0 references
transaction backout
0 references
distributed databases
0 references
NP-complete
0 references
dynamic programming
0 references