]> granicus.if.org Git - postgresql/commit
projects / postgresql / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 192d1bb) | patch
Verify range bounds to bms_add_range when necessary
authorAlvaro Herrera <alvherre@alvh.no-ip.org>
Mon, 30 Jul 2018 21:03:19 +0000 (17:03 -0400)
committerAlvaro Herrera <alvherre@alvh.no-ip.org>
Mon, 30 Jul 2018 22:43:30 +0000 (18:43 -0400)
commita0655ba68fb54a011b1c57901ad66764b1e5473f
tree320f7fe5ca8a5f0bfa6e2cec9603e11622690700tree | snapshot
parent192d1bbf99699de76473184c57fff9ff4b4246f4commit | diff
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
src/backend/executor/nodeAppend.c diff | blob | history
src/backend/partitioning/partprune.c diff | blob | history
Unnamed repository; edit this file 'description' to name the repository.