Re: query plan with index having a btrim is different for strings of different length

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Richard Yen <dba(at)richyen(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: query plan with index having a btrim is different for strings of different length
Date: 2008-12-10 19:34:33
Message-ID: 6020.1228937673@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Richard Yen <dba(at)richyen(dot)com> writes:
> You guys are right. I tried "Miller" and gave me the same result. 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?

If the planner's estimation is that far off then there must be something
very weird about the table statistics, but you haven't given us any clue
what.

regards, tom lane

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Robert Haas 2008-12-10 19:39:42 Re: query plan with index having a btrim is different for strings of different length
Previous Message Richard Yen 2008-12-10 19:28:43 Re: query plan with index having a btrim is different for strings of different length