[wp-trac] [WordPress Trac] #20316: Garbage collect transients

[WordPress Trac]

#20316: Garbage collect transients
----------------------------------------------+----------------------------
 Reporter:  nacin                             |       Owner:
     Type:  enhancement                       |      Status:  new
 Priority:  normal                            |   Milestone:  Future
Component:  Database                          |  Release
 Severity:  normal                            |     Version:
 Keywords:  dev-feedback has-patch 3.7-early  |  Resolution:
----------------------------------------------+----------------------------

Comment (by dartiss):

 Having worked on the aforementioned plugin to provide this functionality
 can I highlight two concerns that need to be considered?

 1. As a user has mentioned above some people have a LARGE number of
 expired transients. Can I suggest that whichever package this is
 implemented in should perform a total wipe of transient data even if a
 database upgrade is not due? Although it will only affect the first run,
 performance does need to be considered - a single SQL statement (or as few
 as possible) if at all possible.
 2. I have also experienced issues with orphaned transients - where one of
 the transient record pairs has either gone missing or, due to truncation
 of the name, are now mis-matched. This will mean that the regular
 housekeeping is likely to miss these but I would suggest that the database
 upgrade 'clear all' should handle these. In my case I've, basically,
 performed a delete on the options table for all '_transient_' records -
 it's rough and basic but is needed to ensure that all transients truly are
 removed.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/20316#comment:28>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software