Large amount of _transient_timeout_feed_% in database

  • Resolved Manni79

    (@manni79)


    2 years ago

    Hello Feedzy Support Team,

    We have a very large amount of database entries in table wp_options, which have in column “option_name” values like ‘transient_timeout_feed_%’

    Two questions:

    • Is Feedzy collecting feed data in wp_options table, which start with transient_timeout_feed_***?
    • If it does, do you have any idea why these data, in our case, getting larger and larger? I cleaned the database table, but before that, there was already 1 GB (!) of data of these entries.

    Thanks a lot
    Manni

    • This topic was modified 2 years ago by Manni79.
Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support Vytis

    (@bvytis)

    Hi @manni79,

    Thank you for sharing the problem with us. It was fixed and with the latest release, it shouldn’t be happening anymore.

    Please make sure to update plugin and let us know if you’re still facing it.

    Thread Starter Manni79

    (@manni79)

    Hi @bvytis ,

    Thank you for your information. But I cleared the database when I created the post. And now the table again has 11.209 total rows of this kind:
    select * from wp_options where option_name like 'transient_timeout_feed%'
    And again 100 MiB of data.

    My WP Plugins page shows no available update. The Version is 4.2.1. (seems to be from 2023-02-27)

    So for me, it seems I have the last updated version. And the problem still exists.

    What details do you need to fix that?
    I can’t run it with that “bug”, because my database is exploding after a few weeks. ??

    Thanks a lot!

    • This reply was modified 2 years ago by Manni79.
    Thread Starter Manni79

    (@manni79)

    I have updated the status to “not resolved” as the problem still exists. Maybe I changed the status by mistake on my last comment.

    Plugin Support Vytis

    (@bvytis)

    Hi @manni79,

    Yes, the fix was released with version 4.2.0.

    I tried again and I can’t replicate this problem after the fix so it might be something still cached on your WordPress instance.

    It’s expected to see transient created for each feed that you’re using (shortcode that you add to your pages) but it’s not expected to have multiple transients related to the same feed which was happening before we patched this.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Large amount of _transient_timeout_feed_% in database’ is closed to new replies.