Comment by _1tem

Shouldn't the query planner catch things like this? Sounds like a performance bug if this happens in Postgres.