Re: [HACKERS] Partition-wise join for join between (declaratively) partitioned tables
Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>
On Wed, Jun 6, 2018 at 8:11 AM, Thomas Munro <thomas.munro@enterprisedb.com> wrote: > On Mon, Mar 5, 2018 at 8:13 PM, Rajkumar Raghuwanshi > <rajkumar.raghuwanshi@enterprisedb.com> wrote: >> On Wed, Feb 7, 2018 at 2:00 PM, Ashutosh Bapat >> Changed partition-wise statement to partitionwise. >> Attached re-based patch. >> >>> The patch looks good to me. I don't think we can reduce it further. >>> But we need some tests to test PWJ with default partitions. Marking >>> this as ready for committer. > > Hi Rajkumar, > > partition_join ... FAILED > That made my heart stop for fraction of a second. I thought, something happened which caused partition_join test fail in master. But then I realised you are talking about Rajkumar's patch and test in that patch. I think it's better to start a separate thread discussing his patch, before I loose my heart ;) -- Best Wishes, Ashutosh Bapat EnterpriseDB Corporation The Postgres Database Company
Commits
-
Add test for partitionwise join involving default partition.
- 4513d3a4be0b 12.0 landed
-
Rewrite the code that applies scan/join targets to paths.
- 11cf92f6e2e1 11.0 cited
-
Fix code related to partitioning schemes for dropped columns.
- cf7ab13bfb45 11.0 landed
-
Copy information from the relcache instead of pointing to it.
- 45866c75507f 11.0 landed
-
Basic partition-wise join functionality.
- f49842d1ee31 11.0 landed
-
Associate partitioning information with each RelOptInfo.
- 9140cf8269b0 11.0 landed
-
Expand partitioned table RTEs level by level, without flattening.
- 0a480502b092 11.0 landed
-
Set partitioned_rels appropriately when UNION ALL is used.
- 448aa36e8b96 10.0 landed
- 1555566d9ee1 11.0 landed
-
Remove dedicated B-tree root-split record types.
- 0c504a80cf2e 11.0 cited
-
Assorted preparatory refactoring for partition-wise join.
- e139f1953f29 11.0 cited
-
Teach adjust_appendrel_attrs(_multilevel) to do multiple translations.
- 480f1f4329f1 11.0 cited
-
Avoid unnecessary single-child Append nodes.
- d57929afc706 11.0 cited
-
Revisit handling of UNION ALL subqueries with non-Var output columns.
- dd4134ea56cb 9.2.0 cited