Re: bad query plans for ~ "^string" (and like "string%") (8.3.6) - Mailing list pgsql-performance

From Marinos Yannikos
Subject Re: bad query plans for ~ "^string" (and like "string%") (8.3.6)
Date
Msg-id 49DCABC2.6030406@geizhals.at
Whole thread Raw
In response to bad query plans for ~ "^string" (and like "string%") (8.3.6)  (Marinos Yannikos <mjy@geizhals.at>)
Responses Re: bad query plans for ~ "^string" (and like "string%") (8.3.6)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-performance
Marinos Yannikos wrote:
> (what exactly does ANALYZE look at for text columns? in our case, about
> 7% of the rows match the index condition, so it seems that left-anchored
> regexp/like matches are not evaluated using the gathered
> most-common-value list at all)

oops, I think I gave myself the answer there. Of course the
most-common-value list will not help if all the values that match the
"bad" index condition exist only once, but have a common prefix...

Perhaps Postgres could sample the first few characters separately for
such queries, but it's probably not worth it.

Regards,
  Marinos

pgsql-performance by date:

Previous
From: Marinos Yannikos
Date:
Subject: bad query plans for ~ "^string" (and like "string%") (8.3.6)
Next
From: Robert Haas
Date:
Subject: Re: bad query plans for ~ "^string" (and like "string%") (8.3.6)