Re: [HACKERS] Partition-wise aggregation/grouping
Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>
On Mon, Mar 12, 2018 at 7:49 PM, Jeevan Chalke <jeevan.chalke@enterprisedb.com> wrote: > > > On Mon, Mar 12, 2018 at 6:07 PM, Ashutosh Bapat > <ashutosh.bapat@enterprisedb.com> wrote: >> >> On Fri, Mar 9, 2018 at 4:21 PM, Ashutosh Bapat >> >> GroupPathExtraData now completely absorbs members from and replaces >> OtherUpperPathExtraData. This means that we have to consider a way to >> pass GroupPathExtraData to FDWs through GetForeignUpperPaths(). I >> haven't tried it in this patch. > > > Initially, I was passing OtherUpperPathExtraData to FDW. But now we need to > pass GroupPathExtraData. > > However, since GetForeignUpperPaths() is a generic function for all upper > relations, we might think of renaming this struct to UpperPathExtraData. Add > an UpperRelationKind member to it > Which will be used to distinguish the passed in extra data. But now we only > have extra data for grouping only, I chose not to do that here. But someone, > when needed, may choose this approach. We don't need UpperRelationKind member in that structure. That will be provided by the RelOptInfo passed. The problem here is the extra information required for grouping is not going to be the same for that needed for window aggregate and certainly not for ordering. If we try to jam everything in the same structure, it will become large with many members useless for a given operation. A reader will not have an idea about which of them are useful and which of them are not. So, instead we should try some polymorphism. I think we can pass a void * to GetForeignUpperPaths() and corresponding FDW hook knows what to cast it to based on the UpperRelationKind passed. BTW, the patch has added an argument to GetForeignUpperPaths() but has not documented the change in API. If we go the route of polymorphism, we will need to document the mapping between UpperRelationKind and the type of structure passed in. > >> >> With this patch there's a failure in partition_aggregation where the >> patch is creating paths with MergeAppend with GatherMerge underneath. >> I think this is related to the call >> add_paths_to_partial_grouping_rel() when try_parallel_aggregation is >> true. But I didn't investigate it further. > > > I fixed it. We need to pass is_partial_agg instead of > extra->partial_partitionwise_grouping while calling > add_paths_to_partial_grouping_rel() in case of parallelism. Thanks for investigation and the fix. -- Best Wishes, Ashutosh Bapat EnterpriseDB Corporation The Postgres Database Company
Commits
-
postgres_fdw: Push down partition-wise aggregation.
- 7e0d64c7a57e 11.0 landed
-
Remove 'target' from GroupPathExtraData.
- c1de1a3a8b93 11.0 landed
-
Implement partition-wise grouping/aggregation.
- e2f1eb0ee30d 11.0 landed
-
Don't pass the grouping target around unnecessarily.
- 94150513ec12 11.0 landed
-
Determine grouping strategies in create_grouping_paths.
- b5996c2791f3 11.0 landed
-
Defer creation of partially-grouped relation until it's needed.
- 4f15e5d09de2 11.0 landed
-
Split create_grouping_paths into degenerate and non-degenerate cases.
- 1466bcfa4a83 11.0 landed
-
Pass additional arguments to a couple of grouping-related functions.
- 648a6c7bd815 11.0 landed
-
Fix logic error in add_paths_to_partial_grouping_rel.
- 3bfe957761ac 11.0 landed
-
Minor cleanup of code related to partially_grouped_rel.
- 5e6a63c0d102 11.0 landed
-
Add a new upper planner relation for partially-aggregated results.
- 3bf05e096b9f 11.0 landed
-
Charge cpu_tuple_cost * 0.5 for Append and MergeAppend nodes.
- 7d8ac9814bc9 11.0 landed
-
Rename enable_partition_wise_join to enable_partitionwise_join
- 2fb1abaeb016 11.0 cited
-
Factor some code out of create_grouping_paths.
- 9fd8b7d63257 11.0 landed
-
Pad XLogReaderState's main_data buffer more aggressively.
- 8735978e7aeb 11.0 cited
-
Prevent int128 from requiring more than MAXALIGN alignment.
- 7518049980be 11.0 cited
-
Fix DROP SUBSCRIPTION hang
- 8edacab20995 11.0 cited
-
Inject $(ICU_LIBS) regardless of platform.
- 66ed3829df95 11.0 cited
-
Some preliminary refactoring towards partitionwise join.
- c44c47a773bd 10.0 cited