summaryrefslogtreecommitdiff
path: root/docs/database.txt
diff options
context:
space:
mode:
authorPierre Schmitz <pierre@archlinux.de>2015-06-04 07:31:04 +0200
committerPierre Schmitz <pierre@archlinux.de>2015-06-04 07:58:39 +0200
commitf6d65e533c62f6deb21342d4901ece24497b433e (patch)
treef28adf0362d14bcd448f7b65a7aaf38650f923aa /docs/database.txt
parentc27b2e832fe25651ef2410fae85b41072aae7519 (diff)
Update to MediaWiki 1.25.1
Diffstat (limited to 'docs/database.txt')
-rw-r--r--docs/database.txt5
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