pgsql: Verify range bounds to bms_add_range when necessary - Mailing list pgsql-committers

From Alvaro Herrera
Subject pgsql: Verify range bounds to bms_add_range when necessary
Date
Msg-id E1fkH00-0005f7-I0@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Verify range bounds to bms_add_range when necessary

Now that the bms_add_range boundary protections are gone, some
alternative ones are needed in a few places.

Author: Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>
Discussion: https://postgr.es/m/3437ccf8-a144-55ff-1e2f-fc16b437823b@lab.ntt.co.jp

Branch
------
REL_11_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/a0655ba68fb54a011b1c57901ad66764b1e5473f

Modified Files
--------------
src/backend/executor/nodeAppend.c    |  5 +++++
src/backend/partitioning/partprune.c | 11 +++++++++++
2 files changed, 16 insertions(+)


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: pgsql: Ensure we build generated headers at the start of some morecase
Next
From: Tom Lane
Date:
Subject: pgsql: Remove dead code left behind by 1b6801051.