Feature Description
tdsql_skip_trans_write_lock specifies whether to skip obtaining the write lock during write operations.
To ensure data consistency and integrity, write operations usually need to be locked. This ensures that when multiple transactions access the same data at the same time, write operations will not interfere with each other, thus avoiding data inconsistency problems. However, in some scenarios, to improve performance, you can choose to skip obtaining transactional write locks to reduce the overhead of lock contention and lock waiting.
Skipping the acquisition of transactional write locks may lead to data inconsistency. Therefore, when using the tdsql_skip_trans_write_lock parameter, carefully evaluate the system's requirements and scenarios to ensure that data consistency and integrity are still maintained even when locking is skipped.
Attribute Description
|
Parameter Type | BOOL |
Default Value | OFF |
Value Range | OFF ON |
Effective Scope | GLOBAL |
Restart Required | No |