diff options
| author | David Rowley <drowley@postgresql.org> | 2022-09-13 11:05:13 +1200 |
|---|---|---|
| committer | David Rowley <drowley@postgresql.org> | 2022-09-13 11:05:13 +1200 |
| commit | c2aa5d01e3e33776f77e68a60ca5b60b58c5c674 (patch) | |
| tree | 9648ba09906e5f7517eddb573ad08ec7155e4644 /src/backend/executor/nodeModifyTable.c | |
| parent | 293a6ac4b9898febe1cf9a4614facf6128be5d77 (diff) | |
| download | postgresql-c2aa5d01e3e33776f77e68a60ca5b60b58c5c674.tar.gz postgresql-c2aa5d01e3e33776f77e68a60ca5b60b58c5c674.zip | |
Don't reference out-of-bounds array elements in brin_minmax_multi.c
The primary fix here is to fix has_matching_range() so it does not
reference ranges->values[-1] when nranges == 0. Similar problems existed
in AssertCheckRanges() too. It does not look like any of these problems
could lead to a crash as the array in question is at the end of the Ranges
struct, and values[-1] is memory that belongs to other fields in the
struct. However, let's get rid of these rather unsafe coding practices.
In passing, I (David) adjusted some comments to try to make it more clear
what some of the fields are for in the Ranges struct. I had to study the
code to find out what nsorted was for as I couldn't tell from the
comments.
Author: Ranier Vilela
Discussion: https://postgr.es/m/CAEudQAqJQzPitufX-jR=YUbJafpCDAKUnwgdbX_MzSc93wuvdw@mail.gmail.com
Backpatch-through: 14, where multi-range brin was added.
Diffstat (limited to 'src/backend/executor/nodeModifyTable.c')
0 files changed, 0 insertions, 0 deletions