On Wed, 26 Sep 2012 at 00:55, Christian Kujau wrote:
307 Query REPLACE /* MessageBlobStore::updateModule 10.0.0.123 */ INTO `msg_resource` (mr_resource,mr_lang,mr_blob,mr_timestamp) VALUES ('user.tokens','en','{}','20120926011737')
307 Query SELECT /* MessageBlobStore::updateModule 10.0.0.123 */ mr_blob FROM `msg_resource` WHERE mr_resource = 'user.options' AND mr_lang = 'en' LIMIT 1
Looking at the database, the table msg_resource had 1,872,796 rows, using 126MB (out of 167 MB for the whole database, including msg_resource). This is a really small wiki, so I'm not sure why this table had so many records.
According to the documentation[0], this table is used to store "JSON message blobs for the resource loader", whatever that means. In my case, truncating msg_resource did the trick. The wiki is now up & running, msg_resource contains 36 rows.
For the curious mind, this is how it looked before:
mysql> select count(*) as a, mr_resource from msg_resource group by mr_resource order by a; [....] | 7040 | mediawiki.action.watch.ajax | | 7040 | mediawiki.api | | 7040 | mediawiki.api.watch | | 14400 | jquery.client | | 14400 | jquery.cookie | | 14400 | jquery.messageBox | | 14400 | jquery.mwExtension | | 14400 | mediawiki.legacy.ajax | | 14400 | mediawiki.legacy.wikibits | | 14400 | mediawiki.page.startup | | 14400 | mediawiki.util | | 23100 | jquery.makeCollapsible | | 23100 | jquery.mw-jump | | 23100 | jquery.placeholder | | 23100 | mediawiki.user | | 23100 | mediawiki.page.ready | | 23100 | jquery.checkboxShiftClick | | 884736 | user.options | | 884736 | user.tokens | +--------+--------------------------------+ 35 rows in set (2.42 sec)
I'll have to keep an eye on that table. While truncating helped in this case, this still smells like some kind of bug...
Thanks for listening, Christian.
[0] https://www.mediawiki.org/wiki/Manual:Msg_resource_table