Fix bogus logic for combining range-partitioned columns during pruning. gen_prune_steps_from_opexps's notion of how to do this was overly complicated and underly correct.
Per discussion of a report from Alan Jackson (though this fixes only one aspect of that problem). Back-patch to v11 where this code came in. Amit Langote Discussion: https://postgr.es/m/[email protected] Branch ------ master Details ------- https://git.postgresql.org/pg/commitdiff/3922f10646fc79264228ea3f6a7343cc3f8f528a Modified Files -------------- src/backend/partitioning/partprune.c | 46 ++++++--------------------- src/test/regress/expected/partition_prune.out | 27 ++++++++++++++++ src/test/regress/sql/partition_prune.sql | 19 +++++++++++ 3 files changed, 55 insertions(+), 37 deletions(-)
