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

[WordPress Trac]

#20316: Garbage collect transients
----------------------------+------------------
 Reporter:  nacin           |       Owner:
     Type:  task (blessed)  |      Status:  new
 Priority:  normal          |   Milestone:  3.7
Component:  Database        |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  needs-patch     |
----------------------------+------------------
Changes (by nacin):

 * keywords:  dev-feedback has-patch 3.7-early => needs-patch


Comment:

 [http://irclogs.wordpress.org/chanlog.php?channel=wordpress-
 dev&day=2013-09-25&sort=asc#m696246 Per IRC discussion], in which I asked:
 "Should we consider a slightly more conservative different approach to
 transient garbage collection? There is just one valid argument I've heard
 against this: we do not want updates to be blamed for breaking sites." —

 For 3.7, we're going to go with deleting only expired transients, and
 we're going to do this in the same location (so, on every DB upgrade).

 We also need to make sure we clear site_transients from the sitemeta table
 for networks. Forgot about that.

 I've seen a few different SQL queries proposed to do this. We'd like to
 find the cleanest and clearest ones. It shouldn't lock up or crash the
 tables, and it should be safe to run on massive options tables.

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