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: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: Richard Huxton <dev(at)archonet(dot)com>
- Cc: Gaetano Mendola <gmendola(at)mbigroup(dot)it>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org>
- Subject: Re: Wrong plan sequential scan instead of an index one
- Date: Fri, 30 Mar 2007 12:13:00 -0400
Richard Huxton <dev(at)archonet(dot)com> writes: > Ah, but it's got no way of knowing what matches you'll get for > '%anything%'. There's no easy way to get statistics for matching substrings. 8.2 actually tries the match on the most-common-values list, if said list is big enough (I think the threshold is stats target = 100). Not sure if that will help here, though. regards, tom lane
- References:
- Wrong plan sequential scan instead of an index one
- From: Gaetano Mendola
- Re: Wrong plan sequential scan instead of an index one
- From: Richard Huxton
- Re: Wrong plan sequential scan instead of an index one
- From: Gaetano Mendola
- Re: Wrong plan sequential scan instead of an index one
- From: Richard Huxton
- Re: Wrong plan sequential scan instead of an index one
- From: Richard Huxton
- Wrong plan sequential scan instead of an index one
- Prev by Date: Re: Weird performance drop
- Next by Date: Re: Shared buffers, db transactions commited, and write IO on Solaris
- 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: