aboutsummaryrefslogtreecommitdiff
path: root/src/backend/commands/constraint.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2014-01-11 13:41:41 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2014-01-11 13:41:56 -0500
commitf0381680fa480a8794d00566cef21178cd63d74e (patch)
tree1265d4f0672087238414b0c3837718e0fe0fe217 /src/backend/commands/constraint.c
parent799728b0baa5b9f7c8dd6991808d1ed049e83b76 (diff)
downloadpostgresql-f0381680fa480a8794d00566cef21178cd63d74e.tar.gz
postgresql-f0381680fa480a8794d00566cef21178cd63d74e.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/commands/constraint.c')
0 files changed, 0 insertions, 0 deletions