Is this behavior still happening with a new db? It’s possible that there have been a bug, but those indexes are not seen by the event refactor happened in 4.7.0, so they are not cleaned up.