On Dec 10, 2008, at 4:08 PM, Tom Lane wrote:
> Richard Yen <dba(at)richyen(dot)com> writes:
>> Is there any way to tune this so that for the common last names,
>> the query
>> run time doesn't jump from <1s to >300s?
> Well, as near as I can tell there's factor of a couple hundred
> difference between the frequencies of 'smith' and 'smithers', so
> you shouldn't really expect similar runtimes for the two cases.
> Having said that, I still think you should try to index both first
> and last name. Also I wonder whether the index on owner is worth
> having at all. It definitely doesn't seem worthwhile to index the
> entries with owner = -1, since there are so many; so maybe you could
> make it a partial index that excludes those entries, in order to
> the planner from trying to use it for this case.
Created the 2-col index, and the query runs much faster on all
Thanks much for all your help,
In response to
pgsql-performance by date
|Next:||From: Matthew Wakeling||Date: 2008-12-11 13:47:19|
|Subject: Re: Experience with HP Smart Array P400 and SATA drives?|
|Previous:||From: Tom Lane||Date: 2008-12-11 00:08:28|
|Subject: Re: query plan with index having a btrim is different for strings of different length |