Re: [HACKERS] [PERFORM] Planner doesn't look at LIMIT?
Tom Lane wrote: Could be. I went back to look at Sam Mason's report about three weeks ago, and it definitely seems to explain his issue. I've just built a patched version as well and it appears to be doing what I think is the right thing now. I.e. actually picking the plan with the lower cost. Thanks! Sam ---(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
Re: [HACKERS] [PERFORM] Planner doesn't look at LIMIT?
On Fri, 2005-07-22 at 12:20 -0400, Tom Lane wrote: I think that this refutes the original scheme of using the same fuzz factor for both startup and total cost comparisons, and therefore propose the attached patch. Comments? Looks good. I think it explains a few other wierd perf reports also. Best Regards, Simon Riggs ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] [PERFORM] Planner doesn't look at LIMIT?
Simon Riggs [EMAIL PROTECTED] writes: Looks good. I think it explains a few other wierd perf reports also. Could be. I went back to look at Sam Mason's report about three weeks ago, and it definitely seems to explain his issue. The fuzzy cost comparison logic is new in 8.0 so it hasn't had all that much testing... regards, tom lane ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
