Search Postgresql Archives

Re: Unnecessary scan on a partial index slows down query dramatically

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Thanks. I'm not really in a position to upgrade at the moment. I guess
in the short-term I'll tweak the query to work around this (e.g.
removing "status = 3" or adding more refining conditions both seem to
work).

Please let me know if there are configuration settings I should try.

Thanks,
Jimmy


On Fri, Apr 25, 2008 at 12:13 PM, Tom Lane <tgl@xxxxxxxxxxxxx> wrote:
> "Jimmy Choi" <yhjchoi@xxxxxxxxx> writes:
>  > A simple query is executing much slower than expected. When looking at
>  > the query plan, I see a bitmap index scan on a partial index that does
>  > not have any associated index condition. How could that happen?
>
>  Easily --- it thinks that the partial index predicate is useful in
>  itself.
>
>
>  > "vacuum analyze" doesn't solve the problem. I'm running 8.1.5.
>
>  choose_bitmap_and was rewritten (again) in 8.1.9.  Try a newer
>  version.
>
>  http://archives.postgresql.org/pgsql-committers/2007-04/msg00233.php
>
>                         regards, tom lane
>
>  --
>  Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
>  To make changes to your subscription:
>  http://www.postgresql.org/mailpref/pgsql-general
>


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux