On 21/03/12 01:20, [[w:en:User:Madman]] wrote: > This does necessitate having a working copy of MediaWiki, which has to > be patched in two places (a script does this automatically) so it > doesn't attempt to expire blocks (which it would attempt to do even > when $wgReadOnly is set) $wgReadOnly no longer means "don't write to the db ever", but if it gives problems with a ro db, maybe we could fix it somewhere so you don't need to patch it.
> and so the option to force a given index is > ignored (because the Toolserver doesn't have some-- maybe most-- of > those indexes). I think they are there, in the underlying tables. It's just not that we can't view or use them from the views, which is what we access to. It's a pity, when we know the optimum SQL queries using force index, but I see the point of the approach, as they could be abused in tables with only partial columns shown, and private ones covered by the indexes. _______________________________________________ Toolserver-l mailing list ([email protected]) https://lists.wikimedia.org/mailman/listinfo/toolserver-l Posting guidelines for this list: https://wiki.toolserver.org/view/Mailing_list_etiquette
