Re: Wrong plan sequential scan instead of an index one - Mailing list pgsql-performance

From Michael Fuhr
Subject Re: Wrong plan sequential scan instead of an index one
Date
Msg-id 20070330105534.GA1737@winnie.fuhr.org
Whole thread Raw
In response to Re: Wrong plan sequential scan instead of an index one  (Michael Fuhr <mike@fuhr.org>)
Responses Re: Wrong plan sequential scan instead of an index one  (Gaetano Mendola <mendola@bigfoot.com>)
List pgsql-performance
On Fri, Mar 30, 2007 at 04:46:11AM -0600, Michael Fuhr wrote:
> Have you tried increasing the statistics target on l_pvcp.value?
> I ran your queries against canned data in 8.2.3 and better statistics
> resulted in more accurate row count estimates for this and other
> parts of the plan.  I don't recall if estimates for non-leading-character
> matches in earlier versions can benefit from better statistics.

This might work only in 8.2.  I see the following in the Release Notes:

* Improve the optimizer's selectivity estimates for LIKE, ILIKE,
  and regular expression operations (Tom)

--
Michael Fuhr

pgsql-performance by date:

Previous
From: Michael Fuhr
Date:
Subject: Re: Wrong plan sequential scan instead of an index one
Next
From: Gaetano Mendola
Date:
Subject: Re: Wrong plan sequential scan instead of an index one