Change bms_add_range to be a no-op for empty ranges In commit 84940644de93, bms_add_range was added with an API to fail with an error if an empty range was specified. This seems arbitrary and unhelpful, so turn that case into a no-op instead. Callers that require further verification on the arguments or result can apply them by themselves.
This fixes the bug that partition pruning throws an API error for a case involving the default partition of a default partition, as in the included test case. Reported-by: Rajkumar Raghuwanshi <[email protected]> Diagnosed-by: Tom Lane <[email protected]> Discussion: https://postgr.es/m/[email protected] Branch ------ REL_11_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/192d1bbf99699de76473184c57fff9ff4b4246f4 Modified Files -------------- src/backend/nodes/bitmapset.c | 7 +++++-- src/test/regress/expected/partition_prune.out | 15 +++++++++++++++ src/test/regress/sql/partition_prune.sql | 7 +++++++ 3 files changed, 27 insertions(+), 2 deletions(-)
