[Answer Query Using Materialized Views] Compute Aggregations on Materialized Views. #322
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Support origin query has aggregations, compute Aggregations on materilized views whose query don't have Aggegations itself.
Origin query:
Could be rewritten to:
All aggregate functions including count(*) are supported in AQUMV which is not limited to IVM's current aggregate functions: count, sum, avg.
Complex expressions have aggregations, and aggregations with Filter clause are also supported.
Aggs in TargetList
aqumv_process_targetlist() could handle that because all Vars under Aggrefs could be rewritten to mv's columns.
Complex expression have Aggs could be processed as we use a Greedy Algorithem to match target expressions.
Aggs Filter Clause
They could be processed automatically as we process post_quals in aqumv_adjust_sub_matched_expr_mutator().
Count(*)
Expressin count(*) has no explicit Vars, but it still need rows from subplan nodes.
NULL values should be taken into account unlike count(a_column).
An example with AGG FILTER clause(See more details in test cases.)
Compute Aggregations on Materialized Views
Authored-by: Zhang Mingli avamingli@gmail.com
fix #ISSUE_Number
Change logs
Describe your change clearly, including what problem is being solved or what feature is being added.
If it has some breaking backward or forward compatibility, please clary.
Why are the changes needed?
Describe why the changes are necessary.
Does this PR introduce any user-facing change?
If yes, please clarify the previous behavior and the change this PR proposes.
How was this patch tested?
Please detail how the changes were tested, including manual tests and any relevant unit or integration tests.
Contributor's Checklist
Here are some reminders and checklists before/when submitting your pull request, please check them:
make installcheck
make -C src/test installcheck-cbdb-parallel
cloudberrydb/dev
team for review and approval when your PR is ready馃コ