Re: [PERFORM] Re: 512,600ms query becomes 7500ms... but why? Postgres 8.3 query planner quirk?

2010-02-13 Thread Bryce Nesbitt
So how about the removal of the "AND" clause? On a test server, this drops the query from 201204 to 438 ms. Is this just random, or is it a real solution that might apply to any arbitrary combination of words? Attached are three test runs: Total runtime: 201204.972 ms Total runtime: 437.766 ms Tot

Re: [PERFORM] Dell PERC H700/H800

2010-02-13 Thread Scott Marlowe
Recently most of our Dell servers came up for warranty extensions and we decided against it. They're all 3+ years old now and replacement parts are cheaper than the Dell warranty extension. In fact the price Dell quoted us on warranty extension was about twice what these machines are going for on

Re: [PERFORM] 512,600ms query becomes 7500ms... but why? Postgres 8.3 query planner quirk?

2010-02-13 Thread Pierre Frédéric Caillau d
Your Query : SELECT contexts.context_key FROM contexts JOIN articles ON (articles.context_key=contexts.context_key) JOIN matview_82034 ON (contexts.context_key=matview_82034.context_key) WHERE contexts.context_key IN (SELECT context_key FROM article_words JOIN words using (word_key) WHERE