catalog: add mz_replacements system relation #34332
Merged
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.
This PR adds a new
mz_replacementsbuiltin table, exposing the replacement MV relationship.It also adds a
replacingcolumn to theSHOW MATERIALIZED VIEWSoutput, fueled by the newmz_replacementstable. The new colum is only added when theenable_replacement_materialized_viewsfeature flag is enabled, so nothing changes for production users yet.Motivation
Part of https://github.com/MaterializeInc/database-issues/issues/9903
Tips for reviewer
Currently, the thinking is that we should instead have a new column in
mz_materialized_views. However, such a column would be immediately stabilized, so until the feature is ready for GA, we use an unstablemz_replacementstable instead.Checklist
$T ⇔ Proto$Tmapping (possibly in a backwards-incompatible way), then it is tagged with aT-protolabel.