Options table overhead leads to 500 server error

[ryan]

Some hosts are reporting overhead in the range of 600k for options tables. Once it gets this big, 500 server errors result. Perhaps we can query overhead from time to time and issue a warning in the admin if it gets too bloated.

[Mittineague]

Options table bloat has been a problem for a while, it's why I wrote the Clean Options plugin. AFAIK the main problem is from old rss_[hash] and rss_[hash]_ts rows left over from feed caching. Although many plugins/themes do not clean up after themselves when they're removed, I gather from my plugin users that have left feedback that old plugin/theme options are less of a problem.

It seems with the switch from Magpie to SimplePie the cached feed rows are now "transient" and so far, unlike the "rss" rows, they seem to be taking care of themselves.

If this in fact the case, it might be possible to put code in somewhere that will remove all the old "rss" rows.

*Note, if you use regex to remove them, take care not to remove the "rss_excerpt_length", "rss_use_excerpt", or "rss_language" options.

[ryan]

We should definitely remove the old rss cache rows. That can be done during upgrade.

[ryan]

#10728 can be used to clear overhead. That's probably as good as we'll get.

[Denis-de-Bernardy]

re-opening with a patch to flush old magpie junk on upgrades

[hakre]

Changing the SQL query in the patch sothat there is no need for an OR might make this even more simple. Just an Idea, I'm not shure if the two patterns for option names are it for magpie rss. But this will remove a lot of old junk at least.

[ryan]

(In [12210]) Delete old magpie cache options. Props Denis-de-Bernardy. fixes #10592