avamingli opened a new pull request, #1594:
URL: https://github.com/apache/cloudberry/pull/1594

   Previously, GetViewBaseRelids() rejected any query with more than one base 
table, so materialized views defined with JOINs were never registered in 
gp_matview_aux/gp_matview_tables. This meant no status tracking and no 
staleness propagation for join matviews.
   
   Add a recursive helper extract_base_relids_from_jointree() that walks 
RangeTblRef, JoinExpr, and FromExpr nodes to collect all base relation OIDs. 
This is the only C function changed -- the existing downstream infrastructure 
(InsertMatviewTablesEntries, SetRelativeMatviewAuxStatus, 
MaintainMaterializedViewStatus, reference counting) already supports N base 
tables per matview.
   
   This is a first step toward AQUMV support for join queries. Users can also 
inspect a join matview's freshness status manually via gp_matview_aux.
   
   Key behaviors:
   - Self-joins (t1 JOIN t1) are deduplicated to one catalog entry
   - All join types supported: INNER, LEFT, RIGHT, FULL, implicit cross
   - Subquery/function RTEs in FROM are still rejected
   - Partitioned tables in joins propagate DML status correctly
   - Status escalation across multiple base tables works (i→e on delete)
   - Transaction rollback correctly reverts status changes
   
   Includes regression tests for: two/three-table joins, implicit joins, 
self-joins, all outer join types, mixed join types, join with GROUP BY, shared 
base tables across multiple MVs, multi-DML transactions, transaction rollback, 
cross joins, partitioned tables in joins, VACUUM FULL, TRUNCATE, WITH NO DATA, 
and DROP CASCADE.
   
   <!-- Thank you for your contribution to Apache Cloudberry (Incubating)! -->
   
   Fixes #ISSUE_Number
   
   ### What does this PR do?
   <!-- Brief overview of the changes, including any major features or fixes -->
   
   ### Type of Change
   - [ ] Bug fix (non-breaking change)
   - [ ] New feature (non-breaking change)
   - [ ] Breaking change (fix or feature with breaking changes)
   - [ ] Documentation update
   
   ### Breaking Changes
   <!-- Remove if not applicable. If yes, explain impact and migration path -->
   
   ### Test Plan
   <!-- How did you test these changes? -->
   - [ ] Unit tests added/updated
   - [ ] Integration tests added/updated
   - [ ] Passed `make installcheck`
   - [ ] Passed `make -C src/test installcheck-cbdb-parallel`
   
   ### Impact
   <!-- Remove sections that don't apply -->
   **Performance:**
   <!-- Any performance implications? -->
   
   **User-facing changes:**
   <!-- Any changes visible to users? -->
   
   **Dependencies:**
   <!-- New dependencies or version changes? -->
   
   ### Checklist
   - [ ] Followed [contribution 
guide](https://cloudberry.apache.org/contribute/code)
   - [ ] Added/updated documentation
   - [ ] Reviewed code for security implications
   - [ ] Requested review from [cloudberry 
committers](https://github.com/orgs/apache/teams/cloudberry-committers)
   
   ### Additional Context
   <!-- Any other information that would help reviewers? Remove if none -->
   
   ### CI Skip Instructions
   <!--
   To skip CI builds, add the appropriate CI skip identifier to your PR title.
   The identifier must:
   - Be in square brackets []
   - Include the word "ci" and either "skip" or "no"
   - Only use for documentation-only changes or when absolutely necessary
   -->
   
   ---
   <!-- Join our community:
   - Mailing list: 
[[email protected]](https://lists.apache.org/[email protected])
 (subscribe: [email protected])
   - Discussions: https://github.com/apache/cloudberry/discussions -->
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to