data under wp_options #66, #68 ? (5 posts)

  1. stereoroid
    Posted 11 years ago #

    I've been backing up my WordPress database from MySQL using MYSQLDUMP - I have no problems with that, I'm happy to say both backup and restore are going well.

    However, when I examine the SQL data in the backup, I can see that there are huge chunks of data under wp_options #66 (rss_0ff4b43bd116a9d8720d689c80e7dfd4) and #68 (rss_867bd5c64f85878d03a060509cd2f92c) - the latter being the largest. These appear to be entries from the WordPress Development Blog (#66) and entries from random blogs I have never heard of, some of which mention WordPress, some not, over 100KB worth.

    This data is not visible to anyone accessing my site, as far as I can tell. I don't even see all of it on my Dashboard, since all the links are different and take you straight to the servers that own the blogs in question, not to data cached locally.

    I tried deleting those records, which cut the size of my SQL backup in half (230KB ~ 112KB), which did not affect the operation of WordPress, but it was there next time I added a blog entry. So: why is WordPress cacheing this data in the MySQL database on my server, under wp_options, with no clear label?

  2. Lorelle
    Posted 11 years ago #

    I'm not sure, but I think these are related to your spam controls and you should leave them alone.

  3. stereoroid
    Posted 11 years ago #

    No, spam controls are under option #58 ("blacklist_keys"), with other settings related to comment moderation etc. following that. It's all plain text, check it out for yourself.

  4. Kafkaesqui

    Posted 11 years ago #

    Those are caches used by the Dashboard rss feeds.

  5. stereoroid
    Posted 11 years ago #

    I sorta guessed that from the content... but why? I don't need all that information cached on my server where only I can read it. As I said, the Dashboard links to WordPress DevBlogs etc. are not reading from any cache, the links go straight to the relevant sites.

    I wouldn't mind if it didn't double the size of the active database, and what it was was clearly marked, with the option to turn it off. After the recent "link spam" scandal on the Support site, you can be sure I'm not letting anyone else put anything on my site that I don't have control over.

Topic Closed

This topic has been closed to new replies.

About this Topic


No tags yet.