[wp-trac] [WordPress Trac] #22176: Cache the results of the posts_request_ids query

WordPress Trac noreply at wordpress.org
Fri Jul 22 11:20:32 UTC 2022

#22176: Cache the results of the posts_request_ids query
 Reporter:  ryan                                 |       Owner:
                                                 |  spacedmonkey
     Type:  enhancement                          |      Status:  assigned
 Priority:  normal                               |   Milestone:  6.1
Component:  Query                                |     Version:  3.4.2
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch 2nd-opinion has-unit-      |     Focuses:
  tests early needs-testing needs-dev-note       |  performance

Comment (by SergeyBiryukov):

 Replying to [comment:32 dd32]:
 > The question arrises here - Does the benefit of providing caching
 outweigh the slight potential back-compat breakage? I think it does, and
 that anything expecting uncached data should be specifying the
 `cache_results` flag to bypass it already.

 Yes, similar thoughts here.

 Replying to [comment:34 peterwilsoncc]:
 > I could be convinced either way but am leaning to on by default from the
 initial commit

 I'm leaning to on too, not a fan of a new parameter that ends up being
 pretty much the same as the existing one, or has a similar purpose where
 the difference is not quite obvious. Would rather extend the existing one
 and see what may break in practice, if anything :)

Ticket URL: <https://core.trac.wordpress.org/ticket/22176#comment:35>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

More information about the wp-trac mailing list