]> git.ipfire.org Git - thirdparty/postgresql.git/commit
Fix yet another issue with step generation in partition pruning.
authorEtsuro Fujita <efujita@postgresql.org>
Fri, 7 Aug 2020 05:45:02 +0000 (14:45 +0900)
committerEtsuro Fujita <efujita@postgresql.org>
Fri, 7 Aug 2020 05:45:02 +0000 (14:45 +0900)
commit4f26932296057721d7668ec13cfd6af2bb8410ec
treebe663d5dd3c7428fd5ecaf1d4c4470265a68f6c5
parenta2e0cf45c21afbcbc544d1aca8d51d90004aa5d9
Fix yet another issue with step generation in partition pruning.

Commit 13838740f fixed some issues with step generation in partition
pruning, but there was yet another one: get_steps_using_prefix() assumes
that clauses in the passed-in prefix list are sorted in ascending order
of their partition key numbers, but the caller failed to ensure this for
range partitioning, which led to an assertion failure in debug builds.
Adjust the caller function to arrange the clauses in the prefix list in
the required order for range partitioning.

Back-patch to v11, like the previous commit.

Patch by me, reviewed by Amit Langote.

Discussion: https://postgr.es/m/CAPmGK16jkXiFG0YqMbU66wte-oJTfW6D1HaNvQf%3D%2B5o9%3Dm55wQ%40mail.gmail.com
src/backend/partitioning/partprune.c
src/test/regress/expected/partition_prune.out
src/test/regress/sql/partition_prune.sql