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

From: "Robert Haas" <robertmhaas(at)gmail(dot)com>
To: "Richard Yen" <dba(at)richyen(dot)com>
Cc: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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:39:42
Message-ID: 603c8f070812101139p189cc828hef8702f37f952b6d@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

> 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?
> Thanks for the help!

Can you send the output of EXPLAIN ANALYZE for both cases?

...Robert

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Scott Marlowe 2008-12-10 19:41:37 Re: Experience with HP Smart Array P400 and SATA drives?
Previous Message Tom Lane 2008-12-10 19:34:33 Re: query plan with index having a btrim is different for strings of different length