Re: Collect frequency statistics for arrays
От | Tom Lane |
---|---|
Тема | Re: Collect frequency statistics for arrays |
Дата | |
Msg-id | 7257.1330547993@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: Collect frequency statistics for arrays (Alexander Korotkov <aekorotkov@gmail.com>) |
Ответы |
Re: Collect frequency statistics for arrays
Re: Collect frequency statistics for arrays |
Список | pgsql-hackers |
Alexander Korotkov <aekorotkov@gmail.com> writes: > On Mon, Jan 23, 2012 at 7:58 PM, Noah Misch <noah@leadboat.com> wrote: >> I've attached a new version that includes the UINT64_FMT fix, some edits of >> your newest comments, and a rerun of pgindent on the new files. I see no >> other issues precluding commit, so I am marking the patch Ready for >> Committer. >> If I made any of the comments worse, please post another update. > Changes looks reasonable for me. Thanks! I am starting to look at this patch now. I'm wondering exactly why the decision was made to continue storing btree-style statistics for arrays, in addition to the new stuff. The pg_statistic rows for array columns tend to be unreasonably wide already, and as-is this patch will make them quite a lot wider. I think it requires more than a little bit of evidence to continue storing stats that seem to have only small probability of usefulness. In particular, if we didn't store that stuff, we'd not need to widen the number of columns in pg_statistic, which would noticeably reduce both the footprint of the patch and the probability of breaking external code. regards, tom lane
В списке pgsql-hackers по дате отправления: