-
Notifications
You must be signed in to change notification settings - Fork 189
Cherry-pick AOCS related work that changes catalog version #1008
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
cool, need a rebase. |
|
Hi @reshke would you like to include this PR in the coming 2.0.0? If so, welcome to add this PR to the GitHub project. |
gfphoenix78
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
big thanks to @gfphoenix78 for taking care of it.... |
HI! lets approve it and merge |
On first index creation (block directory is created) and only that time all columns are scanned. Later any index creation just scans needed columns. cherry-picked. Note influence of greenplum-db/gpdb-archive@8c92aa0
We can get indexes for blkdir and visimap from pg_index via `RelationGetIndexList`. Removing these 2 fields will reduce catalog size. Basically, we now deal with these two properties in a more similar way as the indexes of toast tables, where we always open the toast table first and then get its index via `RelationGetIndexList`. In fact, in majority of the places currently we already have those two aux tables opened. The only place we didn't is in ATExecSetTableSpace(), but it shouldn't slow down that function too much anyway. The other notable thing is that we need to modify how we get these indexes in pg_dump - we now have to check the pg_index.
|
Did a rebase on fresh master |
While working on issue #989 I realized we need to cherry-pick a couple of valuable contributions from GP7 to resolve diff easily. Also, there is a benefit of cherry-picking catalog-changing contributions before CBDB 2.0 release.
What does this PR do?
Type of Change
Breaking Changes
Test Plan
make installcheckmake -C src/test installcheck-cbdb-parallelImpact
Performance:
User-facing changes:
Dependencies:
Checklist
Additional Context
CI Skip Instructions