Re: Wrong result when enable_partitionwise_join is on if collation of PartitionKey and Column is different.
jian he <jian.universality@gmail.com>
From: jian he <jian.universality@gmail.com>
To: Tender Wang <tndrwang@gmail.com>
Cc: Amit Langote <amitlangote09@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2024-10-30T03:57:35Z
Lists: pgsql-hackers
Attachments
- partition_wise_join_collation.sql (application/sql)
- v2-0001-partition_wise_join_collation_check.diff (text/x-patch) patch v2-0001
I missed a case when column collation and partition key collation are the same and indeterministic. that should be fine for partition-wise join. so v2 attached. have_partkey_equi_join, match_expr_to_partition_keys didn't do any collation related check. propose v2 change disallow partitionwise join for case when column collation is indeterministic *and* is differ from partition key's collation. the attached partition_wise_join_collation.sql is the test script. you may use it to compare with the master behavior.
Commits
-
Disallow partitionwise join when collations don't match
- 075acdd93388 18.0 landed
- a0cdfc889367 17.1 landed
- f734b6b4d0cc 16.5 landed
- 33040b1715c7 15.9 landed
- 62df5484f976 14.14 landed
- 054701a2b77a 13.17 landed
- 9c4757491683 12.21 landed
-
Disallow partitionwise grouping when collations don't match
- 90fe6251c816 18.0 landed
- b6484ca9535e 17.1 landed
- dd2f8ebee221 16.5 landed
- 0a620659c549 15.9 landed
- 96f9b29a3e1e 14.14 landed
- ff65f695c0d3 13.17 landed
- 46d9be5efb1a 12.21 landed