Use a parameterized log for sub-optimal transaction logging
authorErik Bernhardson <ebernhardson@wikimedia.org>
Wed, 5 Oct 2016 19:30:18 +0000 (12:30 -0700)
committerErik Bernhardson <ebernhardson@wikimedia.org>
Wed, 5 Oct 2016 19:30:18 +0000 (12:30 -0700)
commit44da55fffb7142a27b010e9eae42b55783410495
tree4340b1ada669752c3bee8152d6cbc92f2e95cb55
parentd8f594f9e68d453113836ba6a9475dd0c51f371b
Use a parameterized log for sub-optimal transaction logging

In logstash these messages can't be grouped in any way, because they are
all slightly different. By using a parameterized log message these can
be grouped to give a better overview about the size of a problem.

Change-Id: Icfa957bd1775b49bccd6e9920586c94eb4597f9b
includes/libs/rdbms/TransactionProfiler.php