No. This is a serious performance problem that was fixed with the last release.

Again - the problem started three years ago before 1.6, @elinw when you added a join from the contact table to the content table -- and there is no relationship between those tables. There is simply no way to join those tables - I wish you could - but relational databases are built on relationships - and there isn't one between content and contacts.

Don't make everyone suffer performance problems -- especially when Mark proved before the last release the GROUP BY didn't fix the problem to begin with.