Skip to content

pkg/executor: report MV refresh and purge statement results#50

Open
windtalker wants to merge 4 commits intomv_testfrom
mv-refresh-stmtctx-result-v2
Open

pkg/executor: report MV refresh and purge statement results#50
windtalker wants to merge 4 commits intomv_testfrom
mv-refresh-stmtctx-result-v2

Conversation

@windtalker
Copy link
Copy Markdown
Owner

What problem does this PR solve?

Issue Number: N/A

Problem Summary:
Reopen the previously merged statement-result change on top of the current mv_test branch.
This keeps the same behavior change for MV refresh / purge statement results after the base branch history moved.

What changed and how does it work?

  • report statement affected rows and last message for fast refresh and complete delta apply from internal executors
  • propagate statement results back to the outer session for all refresh modes and purge materialized view log
  • keep the no-op fast as of timestamp result behavior
  • carry over the targeted regression tests from the previous branch

Check List

Tests

  • Unit test
  • Integration test
  • Manual test (add detailed scripts or steps below)
  • No need to test

Manual test steps:

Side effects

  • Performance regression: Consumes more CPU
  • Performance regression: Consumes more Memory
  • Breaking backward compatibility

Documentation

  • Affects user behaviors
  • Contains syntax changes
  • Contains variable changes
  • Contains experimental features
  • Changes MySQL compatibility

Release note

None

@windtalker windtalker force-pushed the mv-refresh-stmtctx-result-v2 branch from 05b70c2 to a25748f Compare April 3, 2026 13:00
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.

1 participant