[go: nahoru, domu]

Durability (database systems)

This is an old revision of this page, as edited by 106.217.193.9 (talk) at 11:57, 12 November 2019. The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

{{Unreferencesuccessfully been booked, then the seat will remain booked even if the system crashes.

Durability can be achieved by flushing the transaction's log records to non-volatile storage before acknowledging commitment.

In distributed transactions, all participating servers must coordinate before commit can be acknowledged. This is usually done by a two-phase commit protocol.

Many DBMSs implement durability by writing transactions into a transaction log that can be reprocessed to recreate the system state right before any later failure. A transaction is deemed committed only after it is entered in the log.

See also