I was recently horrified to discover that the “wp_options” table of this site was over 1.3 gigabytes in size. For those of you counting at home – that is ENORMOUS and unnecessary. I was confused, because the table seemed to balloon overnight (and likely did balloon overnight, it turns out!).
The issue was caused by a poorly-coded plugin that added some HUGE rows to wp_options. I’m not 100% sure of the culprit nor the specific row, but I’m pretty sure it was either the Jetpack or Spectra plugin that did the ballooning. How do I know this? Well, a manual search (e.g. using phpMyAdmin and my eyeballs) of recent rows in the “wp_options” table turned up a lot of rows that had values that included both “jetpack” and “spectra”.
How I deleted the offending rows and shrunk my “wp_options” table from 1.3gb to 3mb
I used a pretty blunt hammer stroke to fix the issue, running the following 3 sql queries via phpMyAdmin:
- DELETE FROM wp_options where option_name like ‘%jetpack%’;
This removed 180 rows.
- DELETE FROM wp_options where option_name like ‘%spectra%’;
This removed 97 rows.
- DELETE FROM wp_options where option_name like ‘%transient%’;
This removed 51 rows.
So, again, I’m not sure exactly which plugin was the offender, but deleting only 328 rows from my database shaved off over a gigabyte of girth.
Is this helpful?
More posts from themightymo.com
A site we host on Digital Ocean recently went down. It took me a lot of troubleshooting and digging before realizing that the issue was that our disk space was maxed out on Digital Ocean. The site in question needs ~20gb of space, so our 50gb server should be plenty. But alas, there it was…
I was about to send an email to a potential customer pointing them to our 5-star Google Reviews via our Google Business profile (e.g. the Google Map), hoping this added information about our customers’ past experiences might help me close a deal. But when I checked the Google Reviews link, it was down. And after…
I had a Google Search Console issue today where it was seeing a bunch of staging urls that no longer exist. I don’t know how they got there, but here we are. 🙂 To resolve this issue, I had to: That’s it!