feature: Use amflags to support Column-oriented scanning of custom ta… #407
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.
fix #ISSUE_Number
Change logs
For custom tableam, maybe it support column-oriented scanning, the postgres planner can no longer use whether am_handler is aocs table_am to decide whether only to add the columns required by the operator to the targetlist.
If table am supports column-oriented scanning, the flags returned by set_flags set the SCAN_SUPPORT_COLUMN_ORIENTED_SCAN bit.
Why are the changes needed?
I hope that custom column storage can also scan only necessary columns, instead of only aocs table am support
Does this PR introduce any user-facing change?
no
How was this patch tested?
Contributor's Checklist
Here are some reminders and checklists before/when submitting your pull request, please check them:
make installcheck
make -C src/test installcheck-cbdb-parallel
cloudberrydb/dev
team for review and approval when your PR is ready🥳