forked from docs/doc-exports
Lu, Huayi
a24ca60074
Reviewed-by: Hasko, Vladimir <vladimir.hasko@t-systems.com> Co-authored-by: Lu, Huayi <luhuayi@huawei.com> Co-committed-by: Lu, Huayi <luhuayi@huawei.com>
12 lines
1.0 KiB
HTML
12 lines
1.0 KiB
HTML
<a name="EN-US_TOPIC_0000001145894427"></a><a name="EN-US_TOPIC_0000001145894427"></a>
|
|
|
|
<h1 class="topictitle1">Lock Operations</h1>
|
|
<div id="body8662426"><p id="EN-US_TOPIC_0000001145894427__en-us_topic_0059778249_p655714596220"><span id="EN-US_TOPIC_0000001145894427__text261076863">GaussDB(DWS)</span> provides multiple lock modes to control concurrent accesses to table data. These modes are used when Multi-Version Concurrency Control (MVCC) cannot give expected behaviors. Alike, most <span id="EN-US_TOPIC_0000001145894427__text1245379961">GaussDB(DWS)</span> commands automatically apply appropriate locks to ensure that called tables are not deleted or modified in an incompatible manner during command execution. For example, when concurrent operations exist, <strong id="EN-US_TOPIC_0000001145894427__b1243235816346">ALTER TABLE</strong> cannot be executed on the same table.</p>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="dws_04_0542.html">Other Statements</a></div>
|
|
</div>
|
|
</div>
|
|
|