Refactor analyze for PAX
Refactor analyze logic for PAX like AOCO.
Fixes #ISSUE_Number
What does this PR do?
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
Test Plan
- [ ] Unit tests added/updated
- [ ] Integration tests added/updated
- [ ] Passed
make installcheck - [ ] Passed
make -C src/test installcheck-cbdb-parallel
Impact
Performance:
User-facing changes:
Dependencies:
Checklist
- [ ] Followed contribution guide
- [ ] Added/updated documentation
- [ ] Reviewed code for security implications
- [ ] Requested review from cloudberry committers
Additional Context
CI Skip Instructions
Thank you for filing the PR. Compared to the previous PAX analyze logic, does our new implementation method have performance improvements?
AO/CO ANALYZE sampling by combining Knuth's Algorithm S and varblock skipping in this patch
please refer to https://github.com/apache/cloudberry/pull/1241/commits/3807ca3fe0d1ab48323858d4aaecd711d4c06f0c
AO/CO ANALYZE sampling by combining Knuth's Algorithm S and varblock skipping in this patch
please refer to 3807ca3
The number of sampling tuples is less than targrows if dead tuples are selected.