~postgresweekly | Issue 573 - Optimizing queries before planning (9)