I poked around but didn't see this addressed elsewhere - why is url_alias still indexed by a text string ('node/NID')? Every query to this table needs to concatenate a string value prior to the join, so joins are incredibly inefficient. I can understand needing a special case for non-node storage, but when making editorial tools, Views Bulk Operations, or even just large output sets, screen load / query times are just horrible when paths are included in the output.
It would be much better if url_alias had the same entity_type/entity_id/bundle fields that other tables did, or better still, used Entity API for its data storage. I'd even be willing to do this myself - but I wanted to check in with the community on acceptance / desire before starting it.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
The proposal doesn't met the Criteria for evaluating proposed changes → . In this case, there is not demonstrated demand and support for the change.
If there is interest in this re-open the issue and add a comment. Or open a new issue and reference this one.