Re: query plan with index having a btrim is different for strings of different length - Mailing list pgsql-performance

From Tom Lane
Subject Re: query plan with index having a btrim is different for strings of different length
Date
Msg-id 6020.1228937673@sss.pgh.pa.us
Whole thread Raw
In response to Re: query plan with index having a btrim is different for strings of different length  (Richard Yen <dba@richyen.com>)
Responses Re: query plan with index having a btrim is different for strings of different length
List pgsql-performance
Richard Yen <dba@richyen.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

pgsql-performance by date:

Previous
From: Richard Yen
Date:
Subject: Re: query plan with index having a btrim is different for strings of different length
Next
From: "Robert Haas"
Date:
Subject: Re: query plan with index having a btrim is different for strings of different length