No-force

Uses your system voice; voice and rate in settings.

Q7042777Snapshot

≈ 3 min read

Names in other languages

  • EnglishNo-force

Article bodies are English and are not machine-translated. A name in another language is not a translation of the article.

A no-force policy is used in transaction control in database theory. The term no-force refers to the disk pages related to the actual database object being modified. With a no-force policy, when a transaction commits, the changes made to the actual objects are not "forced", that is, required to be written to disk in-place. A record of the changes must still be preserved at commit time to ensure that the transaction is durable. This record is typically written to a sequential transaction log, so that the actual changes to the database objects as recorded on disk can be written at a later time. For frequently changed objects, a no-force policy allows updates to be merged and so reduces the number of write operations to the on-disk database object. A no-force policy also reduces the seek time required for a commit by having mostly sequential write operations to the transaction log, rather than requiring the disk to seek to many distinct database objects during a commit.

A no-force policy is used in transaction control in database theory. The term no-force refers to the disk pages related to the actual database object being modified. With a no-force policy, when a transaction commits, the changes made to the actual objects are not "forced", that is, required to be written to disk in-place. A record of the changes must still be preserved at commit time to ensure that the transaction is durable. This record is typically written to a sequential transaction log, so that the actual changes to the database objects as recorded on disk can be written at a later time. For frequently changed objects, a no-force policy allows updates to be merged and so reduces the number of write operations to the on-disk database object. A no-force policy also reduces the seek time required for a commit by having mostly sequential write operations to the transaction log, rather than requiring the disk to seek to many distinct database objects during a commit.

References

Text derived from https://en.wikipedia.org/w/index.php?oldid=1248210262 under CC BY-SA 4.0; modifications have been made.

Provenance

snapshot no-force-793819-818e5c3e52d539d3 · hash 818e5c3e52d539d370457a36cf14492a2f1a820e262a1f44ec07e4720c9a199c · captured 1727501154.0 · version history

Cite this page as: encyclopegia.org, “No-force”, snapshot no-force-793819-818e5c3e52d539d3. https://encyclopegia.org/a/no-force

Sources cited in this revision

Extracted from the cited revision's reference blocks; absent citations are not invented.