Re: bad query plans for ~ "^string" (and like "string%") (8.3.6)

Список
Период
Сортировка
От Marinos Yannikos
Тема Re: bad query plans for ~ "^string" (and like "string%") (8.3.6)
Дата
Msg-id 49DCABC2.6030406@geizhals.at
обсуждение исходный текст
Ответ на bad query plans for ~ "^string" (and like "string%") (8.3.6)  (Marinos Yannikos)
Ответы Re: bad query plans for ~ "^string" (and like "string%") (8.3.6)  (Tom Lane)
Список pgsql-performance
Дерево обсуждения
bad query plans for ~ "^string" (and like "string%") (8.3.6)  (Marinos Yannikos, )
 Re: bad query plans for ~ "^string" (and like "string%") (8.3.6)  (Marinos Yannikos, )
  Re: bad query plans for ~ "^string" (and like "string%") (8.3.6)  (Tom Lane, )
 Re: bad query plans for ~ "^string" (and like "string%") (8.3.6)  (Robert Haas, )
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 по дате отправления:

Предыдущее
От: Jeff
Дата:
Сообщение: Re: Best replication solution?
Следующее
От: Dimitri Fontaine
Дата:
Сообщение: Re: Best replication solution?