diff options
| author | Luke Shumaker <lukeshu@sbcglobal.net> | 2016-05-01 15:30:02 -0400 |
|---|---|---|
| committer | Luke Shumaker <lukeshu@sbcglobal.net> | 2016-05-01 15:30:02 -0400 |
| commit | 1de335ad3f395ca6861085393ba366a9e3fb4a0d (patch) | |
| tree | f1fdd326034e05177596851be6a7127615d81498 /docs/database.txt | |
| parent | 9c75fa8ff6d4d38ef552c00fef5969fb154765e8 (diff) | |
| parent | f6d65e533c62f6deb21342d4901ece24497b433e (diff) | |
Merge commit 'f6d65'
# Conflicts:
# skins/ArchLinux/ArchLinux.php
Diffstat (limited to 'docs/database.txt')
| -rw-r--r-- | docs/database.txt | 5 |
1 files changed, 1 insertions, 4 deletions
diff --git a/docs/database.txt b/docs/database.txt index 735f26bf..ba3045ed 100644 --- a/docs/database.txt +++ b/docs/database.txt @@ -159,10 +159,7 @@ $dbw->commit( __METHOD__ ); Use of locking reads (e.g. the FOR UPDATE clause) is not advised. They are poorly implemented in InnoDB and will cause regular deadlock errors. -It's also surprisingly easy to cripple the wiki with lock contention. If -you must use them, define a new flag for $wgAntiLockFlags which allows -them to be turned off, because we'll almost certainly need to do so on -the Wikimedia cluster. +It's also surprisingly easy to cripple the wiki with lock contention. Instead of locking reads, combine your existence checks into your write queries, by using an appropriate condition in the WHERE clause of an |