Lock granularity terminology: is the “size of a lock” correctly called lock sizing?

Introduction / Context:
The level at which a lock is applied (row, page, table, database) is an important performance and concurrency concept. The standard term is “lock granularity.” This question checks if “lock sizing” is the correct phrase.

Given Data / Assumptions:

• Granularity affects contention and overhead: fine-grained (row) yields higher concurrency; coarse-grained (table) reduces overhead but may block more.
• Vendors may support lock escalation between granularities.
• Terminology matters for exams and documentation.

Concept / Approach:
“Lock granularity” is the recognized term for the scope/size of locks. “Lock sizing” is not standard; using it may confuse readers and is not used in mainstream database literature.

Step-by-Step Solution:
Identify the concept: size/scope of lock → granularity.Check the label used in texts and manuals.Conclude that “lock sizing” is incorrect terminologically.

Verification / Alternative check:
Look up topics like “lock granularity and escalation” in DBMS documentation; the phrase “lock sizing” rarely appears, if ever.

Why Other Options Are Wrong:
Suggesting NoSQL or key-range exceptions does not change the accepted terminology.

Common Pitfalls:
Using nonstandard vocabulary in audits/designs can lead to miscommunication.

Final Answer:
Invalid statement