|Enable/disable database-intensive features
|其他设置： 按首字母排序 | 按功能排序|
true, disable database-intensive features, so that they can be managed/controlled separately if desired.
This includes reading special pages marked as expensive from the cache instead of regenerating them every time they are requested.
$wgMiserMode set to
true, this means that the special pages managed by this flag will only be updated when explicitly made to update.
For example, setting up a cron-job to call
/maintenance/updateSpecialPages.php or using Extension:RefreshSpecial.
The other disabled features are...
- Disables custom formatting of change sizes in Special:RecentChanges via MediaWiki:Rc-change-size (r48986)
- Disables selecting all pages that start with x box on Special:Log (and
- Totally disables Special:MimeSearch, as well as
famimeoption in the
showsizediffoption of the RSS feed for Special:Contributions
- In the
list=externallinksAPI module, use reduced sorting by namespace mode (returns only a few results when
elnamespaceoption is in use).
- Similarly disables the filter by namespace box on Special:LinkSearch
- Disables showing list of most popular pages on Special:Statistics (but will still show other page view statistics if counters are on)
- Doesn't update number of active users quite on Special:Statistics as often (?)
- Disables the search for images with x somewhere in their name box on Special:NewImages and Special:ListFiles
- Do not show how many previous versions of an image were uploaded on Special:ListFiles
- When running rebuildrecentchanges.php maintenance script, will not re-auto-patrol edits by users with auto-patrol flag.
- When running updateCollation.php maintenance script, will not tell you how many rows in total there are to update.
In MediaWiki 1.23+:
For reference, this wiki has $wgMiserMode on.
You can tell if a wiki has miser mode enabled via the
meta=siteinfo API module.
This configuration option disables update.php in 1.18.0 (and only 1.18.0. Subsequent releases will not use this option for that purpose), requiring one to use
--force to run that script.
Very very very large wikis (like Wikipedia) may need to have more careful upgrade process than the maintenance script does, but most sites would not have to worry about this.