Use custom hash opclass for hash partition pruning This custom opclass was already in use in other tests -- defined independently in every such file. Move the definition to the earliest test that uses it, and keep it around so that later tests can reuse it. Use it in the tests for pruning of hash partitioning, and since this makes the second expected file unnecessary, put those tests back in partition_prune.sql whence they sprang.
Author: Amit Langote Discussion: https://postgr.es/m/CA%2BTgmoZ0D5kJbt8eKXtvVdvTcGGWn6ehWCRSZbWytD-uzH92mQ%40mail.gmail.com Branch ------ master Details ------- https://git.postgresql.org/pg/commitdiff/fafec4cce814b9b15991b62520dc5e5e84655a8a Modified Files -------------- src/test/regress/expected/alter_table.out | 15 +- src/test/regress/expected/hash_part.out | 23 +-- src/test/regress/expected/insert.out | 32 +++- src/test/regress/expected/partition_prune.out | 191 +++++++++++++++++++++ src/test/regress/expected/partition_prune_hash.out | 189 -------------------- .../regress/expected/partition_prune_hash_1.out | 187 -------------------- src/test/regress/parallel_schedule | 2 +- src/test/regress/serial_schedule | 1 - src/test/regress/sql/alter_table.sql | 15 +- src/test/regress/sql/hash_part.sql | 24 +-- src/test/regress/sql/insert.sql | 36 +++- src/test/regress/sql/partition_prune.sql | 44 ++++- src/test/regress/sql/partition_prune_hash.sql | 41 ----- 13 files changed, 305 insertions(+), 495 deletions(-)
