Josh Berkus <josh@agliodbs.com> writes: >> > I actually think the way to attack this issue is to discuss the kinds >> > of errors the planner makes, and what tweaks we could do to correct >> > them. Here's the ones I'm aware of: >> > >> > -- Incorrect selectivity of WHERE clause >> > -- Incorrect selectivity of JOIN >> > -- Wrong estimate of rows returned from SRF >> > -- Incorrect cost estimate for index use >> > >> > Can you think of any others?
-- Incorrect estimate for result of DISTINCT or GROUP BY. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
