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
Please let me know if there are configuration settings I should try.
On Fri, Apr 25, 2008 at 12:13 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "Jimmy Choi" <yhjchoi(at)gmail(dot)com> 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
> > "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
> regards, tom lane
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
In response to
pgsql-general by date
|Next:||From: Andrew Sullivan||Date: 2008-04-25 16:39:33|
|Subject: Re: Unnecessary scan on a partial index slows down query dramatically|
|Previous:||From: Tom Lane||Date: 2008-04-25 16:13:55|
|Subject: Re: Unnecessary scan on a partial index slows down query dramatically |