Fix ALTER MATERIALIZED VIEW ... REBALANCE#2246
Merged
whitehawk merged 1 commit intofeature/ADBDEV-6608from Feb 13, 2026
Merged
Conversation
ShapatinAA
approved these changes
Feb 12, 2026
silent-observer
approved these changes
Feb 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fix 'ALTER MATERIALIZED VIEW ... REBALANCE' command
Problem description:
Attempts to rebalance a materialized view via
'ALTER MATERIALIZED VIEW ... REBALANCE' command (or via equivalently working for
materialized views 'ALTER TABLE ... REBALANCE') ended with an error:
'ERROR: cannot change materialized view ...'
Root cause:
The table rebalance logic tried to insert the data directly into the
materialized view as if it were an ordinary table. It is prohibited for
materialized views.
Fix:
Skip the call of 'ATExecShrinkTable()' for the materialized views. So during
'ALTER ... REBALANCE' only the distribution policy for the materialized view is
updated. And the user needs to perform 'REFRESH MATERIALIZED VIEW ...' after
the rebalance.