diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2014-01-11 13:41:41 -0500 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2014-01-11 13:42:42 -0500 |
commit | 6286526207d53e5b31968103adb89b4c9cd21499 (patch) | |
tree | 17a39e834ce2e3588e298acdb92b3f385fa5533f /src/backend/tcop/postgres.c | |
parent | fd2ace802811c333b0b4e1a28b138fd4774745f3 (diff) | |
download | postgresql-6286526207d53e5b31968103adb89b4c9cd21499.tar.gz postgresql-6286526207d53e5b31968103adb89b4c9cd21499.zip |
Fix compute_scalar_stats() for case that all values exceed WIDTH_THRESHOLD.
The standard typanalyze functions skip over values whose detoasted size
exceeds WIDTH_THRESHOLD (1024 bytes), so as to limit memory bloat during
ANALYZE. However, we (I think I, actually :-() failed to consider the
possibility that *every* non-null value in a column is too wide. While
compute_minimal_stats() seems to behave reasonably anyway in such a case,
compute_scalar_stats() just fell through and generated no pg_statistic
entry at all. That's unnecessarily pessimistic: we can still produce
valid stanullfrac and stawidth values in such cases, since we do include
too-wide values in the average-width calculation. Furthermore, since the
general assumption in this code is that too-wide values are probably all
distinct from each other, it seems reasonable to set stadistinct to -1
("all distinct").
Per complaint from Kadri Raudsepp. This has been like this since roughly
neolithic times, so back-patch to all supported branches.
Diffstat (limited to 'src/backend/tcop/postgres.c')
0 files changed, 0 insertions, 0 deletions