Attached is a patch to optimize the select queries in Site verifcation to use the slave database when configured and available. Could this be incorporated? Thanks!

Members fund testing for the Drupal project. Drupal Association Learn more


amanaplan’s picture

Status: Active » Needs review
Dave Reid’s picture

Core doesn't seem to establish a pattern of using slave servers when using queries in validation or load hooks, so I'm very hesitant to approve those changes.

amanaplan’s picture

644 bytes

Definitely understood and a valid hesitation. What do you think about just using slave servers to query the verification meta tags to add to the front page? It may seem pretty insignificant, but I'm trying to reduce overall master database load on the front page for logged in users (where a lot of activity is occurring and Varnish, of course, is not an option). Many thanks for your time.

joachim’s picture

Issue summary: View changes
Status: Needs review » Closed (won't fix)

This seems to me to definitely be something that should be handled at the core level -- the connection object has the ability to have default options for all queries:!database! I imagine those can be set somehow. If not, then that's a core bug. It shouldn't be necessary to patch all contrib modules in this way!