review-correctness-query-planner-execution

Review database query planner changes for behavioral correctness by running static analysis on pull request diffs to enforce domain invariants and preserve operator semantics. This identifies regression risks in optimizer rewrites and predicate pushdown logic before merge.

When modifying SQL execution operators and stream tokenization, check edge cases like chunked record framing boundaries, reverse and forward scan paths, and pushdown operator preservation. Specialized validation gates catch these boundary-related regressions in execution engine code.

Static analysis detects query regression risks by performing diff-focused review of database engine code changes without running build or test commands. It applies a mandatory correctness checklist covering SQL semantics, parser binding rules, and execution operator contracts to keep latency low.

Yes, you can use diff-based static analysis to validate optimizer rewrites and predicate pushdown in SQL. It systematically verifies that logic correctly handles NULL values and outer-join semantics, ensuring behavior-preservation requirements are met before merging.

You need a correctness checklist for reviewing database execution engine code changes when diffs touch SQL parsing, query binding, optimizer logic, or execution operators. It enforces domain invariants and catches subtle semantic corruption that standard reviews easily miss.

Static analysis for catching query planner regressions is limited to diff-focused review without executing build or test commands. It excels at semantic boundary validation but cannot replace dynamic runtime testing for verifying actual stream tokenization and chunked record framing execution paths.