Re: [HACKERS] advanced partition matching algorithm forpartition-wise join - Mailing list pgsql-hackers

Thanks for the update version.  

583 + * The function returns NULL if we can not find the matching pair of
 584 + * partitions. This happens if 1. multiple partitions on one side match with
 585 + * one partition on the other side. 2. a given partition on the outer side
 586 + * doesn't have a matching partition on the inner side. We can not support the
 587 + * first case since we don't have a way to represent multiple partitions as a
 588 + * single relation (RelOptInfo) and then perform join using the ganged
 589 + * relation. We can not support the second case since the missing inner
 590 + * partition needs to be represented as an empty relation and we don't have a
 591 + * way to introduce empty relation during join planning after creating paths
 592 + * for all the base relations.
 593 + */
 594 +PartitionBoundInfo
 595 +partition_bounds_merge(int partnatts,

I think the second condition mention for partition_bounds_merge() looks
outdated, do you think we should remove that or am I missing something here?

1768 +
1769 +       /*
1770 +        * If this is an outer join, the merged partition would act as the
1771 +        * default partition of the join; record the index in *default_index
1772 +        * if not done yet.
1773 +        */
1774 +       if (jointype == JOIN_LEFT || jointype == JOIN_ANTI ||
1775 +           jointype == JOIN_FULL)
1776 +       {

As decided need to replace this list by IS_OUTER_JOIN(jointype).

2020 +       if (jointype == JOIN_LEFT || jointype == JOIN_FULL ||
2021 +           jointype == JOIN_ANTI)
2022 +       {

Same as the previous.
I tried a coverage testing and tried to adjust & add a few tests to improved the
code coverage for the v25 patch. Please have a look at the attached 0002 & also
attach the coverage output with & without this patch, TWIMW.