diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2013-07-24 00:44:09 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2013-07-24 00:44:46 -0400 |
| commit | 13f11c8a8cd0f696fc5f4aead96344e4a6173448 (patch) | |
| tree | 1bd9a166a649942383138c0ca253d6b7c70587bb /src/backend/executor/nodeFunctionscan.c | |
| parent | 15fdf7302a99b0f63394bc49c2528b4731a6627e (diff) | |
| download | postgresql-13f11c8a8cd0f696fc5f4aead96344e4a6173448.tar.gz postgresql-13f11c8a8cd0f696fc5f4aead96344e4a6173448.zip | |
Fix booltestsel() for case where we have NULL stats but not MCV stats.
In a boolean column that contains mostly nulls, ANALYZE might not find
enough non-null values to populate the most-common-values stats,
but it would still create a pg_statistic entry with stanullfrac set.
The logic in booltestsel() for this situation did the wrong thing for
"col IS NOT TRUE" and "col IS NOT FALSE" tests, forgetting that null
values would satisfy these tests (so that the true selectivity would
be close to one, not close to zero). Per bug #8274.
Fix by Andrew Gierth, some comment-smithing by me.
Diffstat (limited to 'src/backend/executor/nodeFunctionscan.c')
0 files changed, 0 insertions, 0 deletions