From d8807daaf6b23c73beaf176ad632fd662569c23b Mon Sep 17 00:00:00 2001 From: Kevin Israel Date: Mon, 27 Oct 2014 23:32:22 -0400 Subject: [PATCH] docs/database.txt: Don't mention $wgAntiLockFlags Setting was removed in 12757b50f8da and is no longer used on the Wikimedia cluster. Change-Id: I0a6e0c029d3246f7a5a229411e66949469ab941e --- docs/database.txt | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/docs/database.txt b/docs/database.txt index 735f26bff3..ba3045ed40 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 -- 2.20.1