On Fri, 30 Nov 2007, cluster wrote: > Can anyone explain the following odd behavior? > I have a query that completes in about 90 ms. If I append LIMIT to the > very end, eg. "LIMIT 500" the evaluation time increases to about 800 ms. > How can performance get *worse* by giving the database the option to > stop the evaluation earlier (when it reaches the output 500 rows)?
The planner doesn't always get it right. Simple. Have you done a "VACUUM FULL ANALYSE" recently? Matthew -- It is better to keep your mouth closed and let people think you are a fool than to open it and remove all doubt. -- Mark Twain ---------------------------(end of broadcast)--------------------------- TIP 2: Don't 'kill -9' the postmaster
