]> granicus.if.org Git - postgresql/commit
projects / postgresql / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 1b68010) | 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:45:39 +0000 (18:45 -0400)
commitd25d45e4d9221948e6b0d80ce22ce559e99c2f48
treeef84c7447dbd667e20a982ecfe2f68c05259e0ectree | snapshot
parent1b68010518c9d2ede24e6c721a9c0dc82c358fb1commit | 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/executor/nodeMergeAppend.c diff | blob | history
src/backend/partitioning/partprune.c diff | blob | history
Unnamed repository; edit this file 'description' to name the repository.