Last modified: 2012-11-28 14:02:23 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T43593, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 41593 - Add global to prevent writing to wb_changes database table
Add global to prevent writing to wb_changes database table
Status: VERIFIED FIXED
Product: MediaWiki extensions
Classification: Unclassified
WikidataRepo (Other open bugs)
unspecified
All All
: High enhancement (vote)
: ---
Assigned To: Wikidata bugs
:
: 41594 (view as bug list)
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-10-31 16:59 UTC by Sam Reed (reedy)
Modified: 2012-11-28 14:02 UTC (History)
4 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Sam Reed (reedy) 2012-10-31 16:59:03 UTC
The wb_changes table on wikidatawiki reached 1GB today. As this is currently not used, it's wasted space, and truncating the table doesn't free the used disk space (dropping and reimporting the database would be necessary). However, truncating it will mean the space on will not grow until the tables once again fill all that disk space.

On this note, it'd be really handy to have a global to disable/enable writing to that table. In the current setup, this is un-needed and unused, and according to Denny, is subject to major change soon. It does save numerous of large insert statements to the master, saving some overhead
Comment 1 Sam Reed (reedy) 2012-10-31 17:27:38 UTC
*** Bug 41594 has been marked as a duplicate of this bug. ***
Comment 2 Daniel Kinzler 2012-10-31 19:55:54 UTC
Fix posted as I2348d008.

Set $wgWBSettings['useChangesTable'] = false; to disable the wb_changes table.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links