Skip to content

Conversation

@teskje
Copy link
Contributor

@teskje teskje commented Dec 16, 2025

This PR adds an additional check in materialzied view planning, to reject replacement MVs whose queries depend on the replacement target. We can't allow those because after applying the replacement we would end up with an object that depends on itself.

Motivation

  • This PR fixes a recognized bug.

Fixes https://github.com/MaterializeInc/database-issues/issues/9962

Checklist

  • This PR has adequate test coverage / QA involvement has been duly considered. (trigger-ci for additional test/nightly runs)
  • This PR has an associated up-to-date design doc, is a design doc (template), or is sufficiently small to not require a design.
  • If this PR evolves an existing $T ⇔ Proto$T mapping (possibly in a backwards-incompatible way), then it is tagged with a T-proto label.
  • If this PR will require changes to cloud orchestration or tests, there is a companion cloud PR to account for those changes that is tagged with the release-blocker label (example).
  • If this PR includes major user-facing behavior changes, I have pinged the relevant PM to schedule a changelog post.

This commit adds an additional check in materialzied view planning, to
reject replacement MVs whose queries depend on the replacement target.
We can't allow those because after applying the replacement we would end
up with an object that depends on itself.
@teskje teskje requested a review from a team as a code owner December 16, 2025 10:33
@teskje teskje requested review from aljoscha and antiguru December 16, 2025 10:33
Copy link
Member

@antiguru antiguru left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants