Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Wrong plan sequential scan instead of an index one
- From: Michael Fuhr <mike(at)fuhr(dot)org>
- To: Gaetano Mendola <mendola(at)bigfoot(dot)com>
- Cc: "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org>, Claus Guttesen <kometen(at)gmail(dot)com>
- Subject: Re: Wrong plan sequential scan instead of an index one
- Date: Fri, 30 Mar 2007 04:55:34 -0600
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
- Follow-Ups:
- Re: Wrong plan sequential scan instead of an index one
- From: Gaetano Mendola
- Re: Wrong plan sequential scan instead of an index one
- References:
- Wrong plan sequential scan instead of an index one
- From: Gaetano Mendola
- Re: Wrong plan sequential scan instead of an index one
- From: Claus Guttesen
- Re: Wrong plan sequential scan instead of an index one
- From: Gaetano Mendola
- Re: Wrong plan sequential scan instead of an index one
- From: Michael Fuhr
- Wrong plan sequential scan instead of an index one
- Prev by Date: Re: Wrong plan sequential scan instead of an index one
- Next by Date: Re: Wrong plan sequential scan instead of an index one
- Previous by thread: Re: Wrong plan sequential scan instead of an index one
- Next by thread: Re: Wrong plan sequential scan instead of an index one
- Indexes: