Re: Performance Anomaly with "col in (A,B)" vs. "col = A OR col = B" ver. 9.0.3

Поиск
Список
Период
Сортировка
От Craig James
Тема Re: Performance Anomaly with "col in (A,B)" vs. "col = A OR col = B" ver. 9.0.3
Дата
Msg-id 4E80B3F9.8070001@emolecules.com
обсуждение исходный текст
Ответ на Re: Performance Anomaly with "col in (A,B)" vs. "col = A OR col = B" ver. 9.0.3  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: Performance Anomaly with "col in (A,B)" vs. "col = A OR col = B" ver. 9.0.3  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-performance
On 9/26/11 10:07 AM, Tom Lane wrote:
> Cranking up the statistics target for the hts_code_id column (and re-ANALYZEing) ought to fix it. If all your tables
arethis large you might want to just increase default_statistics_target across the board. regards, tom lane  
This is common advice in this forum ....  but what's the down side to increasing statistics?  With so many questions
comingto this forum that are due to insufficient statistics, why not just increase the default_statistics_target?  I
assumethere is a down side, but I've never seen it discussed.  Does it increase planning time?  Analyze time?  Take
lotsof space? 

Thanks,
Craig

В списке pgsql-performance по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: Performance Anomaly with "col in (A,B)" vs. "col = A OR col = B" ver. 9.0.3
Следующее
От: Tom Lane
Дата:
Сообщение: Re: Performance Anomaly with "col in (A,B)" vs. "col = A OR col = B" ver. 9.0.3