25bb9b12c1
MySQL optimiser seems to prefer a full table scan of `post-user` table in the count query mentioned in issue #14763. When the origin and deleted columns are added to the index, the IN-query part of the query can be done with index-only scan, which is much faster. Adding the columns in the order uri-id, origin, deleted allows some other queries to also use it when checking for uri-id and origin. Fixes #14763 |
||
|---|---|---|
| .. | ||
| activitystreams.jsonld | ||
| apschema.jsonld | ||
| dbstructure.config.php | ||
| dbview.config.php | ||
| defaults.config.php | ||
| dependencies.config.php | ||
| did-v1.jsonld | ||
| env.config.php | ||
| funkwhale.audio.jsonld | ||
| identity-v1.jsonld | ||
| joinmastodon.jsonld | ||
| litepub-0.1.jsonld | ||
| platforms.config.php | ||
| routes.config.php | ||
| schema.jsonld | ||
| security-data-integrity-v1.jsonld | ||
| security-multikey-v1.jsonld | ||
| security-v1.jsonld | ||
| settings.config.php | ||
| socialweb-webfinger.jsonld | ||
| strategies.config.php | ||