diff options
| author | Tomas Vondra <tomas.vondra@postgresql.org> | 2023-05-18 13:00:31 +0200 |
|---|---|---|
| committer | Tomas Vondra <tomas.vondra@postgresql.org> | 2023-05-18 23:34:35 +0200 |
| commit | 2b1ab28b9dc9226b8a87cf8886ac3aebe591ac9a (patch) | |
| tree | 4efadfa72d11993b9726c8ade61ca385964b0696 /contrib/intarray/_intbig_gist.c | |
| parent | 0409c7fc746b2597edeaab3132d3f3554660283d (diff) | |
| download | postgresql-2b1ab28b9dc9226b8a87cf8886ac3aebe591ac9a.tar.gz postgresql-2b1ab28b9dc9226b8a87cf8886ac3aebe591ac9a.zip | |
Fix handling of NULLs when merging BRIN summaries
When merging BRIN summaries, union_tuples() did not correctly update the
target hasnulls/allnulls flags. When merging all-NULL summary into a
summary without any NULL values, the result had both flags set to false
(instead of having hasnulls=true).
This happened because the code only considered the hasnulls flags,
ignoring the possibility the source summary has allnulls=true.
Discovered while investigating issues with handling empty BRIN ranges
and handling of NULL values, but it's a separate problem (has nothing to
do with empty ranges).
Fixed by considering both flags on the source summary, and updating the
hasnulls flag on the target summary.
Backpatch to 11. The bug exists since 9.5 (where BRIN indexes were
introduced), but those releases are EOL already.
Discussion: https://postgr.es/m/9d993d0d-e431-2196-9ccc-0554d0e60154%40enterprisedb.com
Diffstat (limited to 'contrib/intarray/_intbig_gist.c')
0 files changed, 0 insertions, 0 deletions