diff options
author | Alvaro Herrera <alvherre@alvh.no-ip.org> | 2018-07-30 17:18:42 -0400 |
---|---|---|
committer | Alvaro Herrera <alvherre@alvh.no-ip.org> | 2018-07-30 18:43:30 -0400 |
commit | 192d1bbf99699de76473184c57fff9ff4b4246f4 (patch) | |
tree | c191e7160f8d23ebc8f899d7b087584225734b8d /src/backend/executor/nodeModifyTable.c | |
parent | 739d9b29948bb508656d7f6c779630788abac560 (diff) | |
download | postgresql-192d1bbf99699de76473184c57fff9ff4b4246f4.tar.gz postgresql-192d1bbf99699de76473184c57fff9ff4b4246f4.zip |
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 <rajkumar.raghuwanshi@enterprisedb.com>
Diagnosed-by: Tom Lane <tgl@sss.pgh.pa.us>
Discussion: https://postgr.es/m/16590.1532622503@sss.pgh.pa.us
Diffstat (limited to 'src/backend/executor/nodeModifyTable.c')
0 files changed, 0 insertions, 0 deletions