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

[WordPress Trac]

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

Comment (by DavidAnderson):

 Deleting all transients, regardless of expiration? Won't that bite a lot
 of people?

 e.g. In UpdraftPlus (http://wordpress.org/plugins/updraftplus - highest
 rated backup plugin), a transient is used to track the job status. A
 backup job may need several attempts to complete (e.g. if it's creating a
 big zip file). Potentially a backup job may be half-complete when the
 transients get cleared. Potentially then I'll get dozens or hundreds of
 support requests (since the plugin has an install base of ~60,000) ("hey,
 what happened to my nightly backup job last night?") every time a new
 WordPress release causes a database upgrade and wipes out the job mid-
 progress.

 I propose that only expired transients should be cleared.

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