Re: best statistic target for boolean columns
От | Tom Lane |
---|---|
Тема | Re: best statistic target for boolean columns |
Дата | |
Msg-id | 3481.1096313192@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: best statistic target for boolean columns (Gregory Stark <gsstark@mit.edu>) |
Ответы |
Re: best statistic target for boolean columns
|
Список | pgsql-performance |
Gregory Stark <gsstark@mit.edu> writes: > No, actually the stats table keeps the n most common values and their > frequency (usually in percentage). So really a target of 2 ought to be enough > for boolean values. In fact that's all I see in pg_statistic; I'm assuming > there's a full histogram somewhere but I don't see it. Where would it be? It's not going to be there. The histogram only covers values that are not in the most-frequent-values list, and therefore it won't exist for a column that is completely describable by most-frequent-values. > However the target also dictates how large a sample of the table to take. A > target of two represents a very small sample. So the estimations could be > quite far off. Right. The real point of stats target for such columns is that it determines how many rows to sample, and thereby indirectly implies the accuracy of the statistics. For a heavily skewed boolean column you'd want a high target so that the number of occurrences of the infrequent value would be estimated accurately. It's also worth noting that the number of rows sampled is driven by the largest per-column stats target in the table, and so reducing stats target to 2 for a boolean column will save *zero* effort unless all the columns in the table are booleans. regards, tom lane
В списке pgsql-performance по дате отправления: