Skip to main content

Timeline for Clean database from unused tables

Current License: CC BY-SA 3.0

10 events
when toggle format what by license comment
Aug 23, 2012 at 9:18 vote accept urok93
Aug 22, 2012 at 8:57 history edited Tom J Nowell CC BY-SA 3.0
added 70 characters in body
Aug 22, 2012 at 8:57 comment added Tom J Nowell That depends if they're marked as autoload, and how much data they contain. Otherwise this classes as micro-optimisation, which is very, very rarely a good thing. You'd be better off optimising elsewhere.
Aug 22, 2012 at 8:30 comment added urok93 Ok Tom, does it affect performance in a significant way if it's bloated? That's the main concern for me. If it's not that important it's ok if there are a few extra rows.
Aug 21, 2012 at 7:42 comment added Tom J Nowell The only reliable way of 'unbloating' the options table is to export all your data and reimport it into a fresh install. Options table will naturally end up with a lot of entries as it's used for transients and many other things. There's no easy reliable way of determining what's left over from old plugins and what isn't
Aug 20, 2012 at 17:11 comment added urok93 Ok, yes I can see the full list of tables. Isn't a bloated wp_options table bad for performance?
Aug 20, 2012 at 13:46 comment added Tom J Nowell Can you not see the full list of tables?
Aug 20, 2012 at 13:45 comment added Tom J Nowell Well you don't have to 'clean' the options table, and I'd strongly recommend against it. Take any suspect table and google for it to see which plugin it belongs to. If you delete a plugin and things break, use your backup to restore the table
Aug 20, 2012 at 11:15 comment added urok93 Thanks, my main problem however is how to discover which tables are no longer needed. Some of them I can identify because I am familiar with them, however other plugins create tables and I'm not aware of those. I have the same problem with the wp_options table which has become bloated.
Aug 20, 2012 at 8:59 history answered Tom J Nowell CC BY-SA 3.0