Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rephrase comment for deferred IVM case #576

Merged
merged 3 commits into from
Aug 25, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 5 additions & 4 deletions src/backend/optimizer/plan/aqumv.c
Original file line number Diff line number Diff line change
Expand Up @@ -174,7 +174,8 @@ answer_query_using_materialized_views(PlannerInfo *root,
/*
* AQUMV
* Currently the data of IVM is always up-to-date if there were.
* Take care of this when IVM defered-fefresh is supported(in SERVERLESS mode).
* However, we place this future-proof condition to take
* care of IVM deferred maintenance/incremental refresh feature (in SERVERLESS mode).
*
* Normal materialized views could also be used if its data is up to date.
*/
Expand Down Expand Up @@ -693,10 +694,10 @@ void aqumv_adjust_simple_query(Query *viewQuery)
* AQUMV
* We have to rewrite now before we do the real Equivalent
* Transformation 'rewrite'.
* Because actions sotored in rule is not a normal query tree,
* it can't be used directly, ex: new/old realtions used to
* Because actions stored in rule is not a normal query tree,
* it can't be used directly, with exception to new/old relations used to
* refresh mv.
* Earse unused relatoins, keep the right one.
* Erase unused relations, keep the right one.
*/
foreach (lc, viewQuery->rtable)
{
Expand Down
Loading