pgsql: Verify range bounds to bms_add_range when necessary

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Verify range bounds to bms_add_range when necessary
Date: 2018-07-30 22:50:44
Message-ID: [email protected]
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: 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(at)lab(dot)ntt(dot)co(dot)jp>
Discussion: https://postgr.es/m/[email protected]

Branch
------
master

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

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

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2018-07-30 23:11:23 pgsql: Remove dead code left behind by 1b6801051.
Previous Message Tom Lane 2018-07-30 22:04:49 pgsql: Ensure we build generated headers at the start of some more case