On Mon, Jun 2, 2008 at 3:43 PM, Justin <[EMAIL PROTECTED]> wrote: > As i've been looking over the more complicated queries that i have written > and gotten allot of help in redoing the quires from you all, thanks again. > > I have noticed that estimated Cost to do the query is way off from Actual. > The queries don't run slow at least not to me. The Estimated Cost is way > higher than the actual time on Hash joins but on the scan through the tables > the Estimate Cost to Actual flips where Actual is way higher than Estimated > Cost > > I have tried increasing and decreasing the Stats on the important columns > with no changes
Well, they're not measured in the same units. estimated costs are in terms of the cost to sequentially scan a single tuple, while actual costs are in milliseconds. You might be able to change the cost of sequential scan from 1 to something else and everything else to reflect that change to get them close. But they aren't supposed to match directly up. -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
