Re: [PERFORM] Query planner making bad decisions

Tom Lane said the following on 05/11/2009 07:02 PM: where we're off by a factor of 1500+ :-( I think most likely the ~~ operator is the biggest problem. Unfortunately 8.1's estimator for ~~ is not terribly bright. You could try increasing your statistics target but I don't think it will help mu

[PERFORM] Query planner making bad decisions

(actual time=1493.343..1726.020 rows=1575 loops=1) Merge Cond: ("outer".id = "inner".customfield) -> Index Scan using customfields_pkey on customfields customfields_1 (cost=0.00..16.41 rows=1 widt