[wp-trac] [WordPress Trac] #14080: Needless wp_cache_delete() inside set_theme_mod()

[WordPress Trac]

#14080: Needless wp_cache_delete() inside set_theme_mod()
--------------------------+-------------------------------------------------
 Reporter:  shidouhikari  |       Owner:     
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  3.1
Component:  Cache         |     Version:     
 Severity:  normal        |    Keywords:     
--------------------------+-------------------------------------------------

Comment(by gazouteast):

 Replying to [comment:4 nacin]:
 > Replying to [comment:3 gazouteast]:
 > > Be careful here - cross refer the wp_options table persistent bloating
 issue, now showing as persisting under Simplepie when originally blamed on
 MagPie - there may be clues here regarding crossover contributories.
 > Please, stop. This has nothing to do with your tickets.

 Nacin - think about it - your knee-jerk reaction was to label the cache
 delete as "cruft" ... and yet, lack of expired cache deletion is the exact
 root symptom of the database bloat in wp_options.  It's like you believe
 nothing should be deleted, ever, and that everyone has got trillions of
 terabytes of database capacity.

 Right now, anything that relates to deleting cache getting removed from
 cache is a bad move - I'm not alone in experiencing the wp_options bloat.

 Apologies to shidouhikari - I'm not trying to hijack - related to this is
 that I also have some wp_options table bloat from non-deleted, expired,
 themes version check entries - it's minor in the overall bloat, but it's
 there - it's a contributory.  I'd make a fairly safe guess that others
 have it too.

 To me it all has a relationship, and the wider effect of knocking out
 "cruft" has to be explored before banging ahead with such a solution.

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