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

From: Bryce Nesbitt <bryce2(at)obviously(dot)com>
To: pgsql-performance(at)postgresql(dot)org
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: Re: 512,600ms query becomes 7500ms... but why? Postgres 8.3 query planner quirk?
Date: 2010-02-13 08:09:26
Message-ID: 4B765E36.20002@obviously.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

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
Total runtime: 341.727 ms

Attachment Content-Type Size
No_AND.txt text/plain 17.5 KB

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Scott Marlowe 2010-02-13 08:31:03 Re: Dell PERC H700/H800
Previous Message Bryce Nesbitt 2010-02-13 07:58:12 Re: 512,600ms query becomes 7500ms... but why? Postgres 8.3 query planner quirk?