Bureaucrats, editor, reviewer, Administrators
13,550
edits
Changes
Jump to navigation
Jump to search
→Concurrency Control
* Subsequent operations (read or write) will be queued until the updating transaction has completed.
Each database has its own queue: An update on database A will not block operations on database B. This is under the premise that it can be statically determined, i.e., before the transaction is evaluated) , which databases will be accessed by a transaction (see [[#Limitations|below]]). The number of maximum parallel transactions can be adjusted with the [[Options#PARALLEL|PARALLEL]] option.
With {{Version|8.6}}, locking has been improved:
* Jobs without database access will never be locked. Globally locking jobs can now be executed in parallel with non-locking jobs.* A {{Option|FAIRLOCK}} option has been added: By default, which is now false by default: Read read transactions will now be favored, and transactions that access no databases can be evaluated even if the maximum transactions limit has been reached.* A globally locking job can now be executed in parallel with a non-locking job.
==External Side Effects==
