This is introduced by GPDB commit ed364586b99.
For AO/AOCS partition tables, it's possible to update across partitions.
And it does have deleteDesc and uniqueCheckDesc if there were.
The DeleteDesc and InsertDesc are not enough to decide if the partition has a update operation or not.
Some partitions have visimap but some not, clean them if possible.
Authored-by: Zhang Mingli avamingli@gmail.com
fix #ISSUE_Number
Change logs
Describe your change clearly, including what problem is being solved or what feature is being added.
If it has some breaking backward or forward compatibility, please clary.
Why are the changes needed?
Describe why the changes are necessary.
Does this PR introduce any user-facing change?
If yes, please clarify the previous behavior and the change this PR proposes.
How was this patch tested?
Please detail how the changes were tested, including manual tests and any relevant unit or integration tests.
Contributor's Checklist
Here are some reminders and checklists before/when submitting your pull request, please check them:
[ ] Make sure your Pull Request has a clear title and commit message. You can take git-commit template as a reference.
[ ] Sign the Contributor License Agreement as prompted for your first-time contribution(One-time setup).
Fix https://github.com/cloudberrydb/cloudberrydb/issues/557.
This issue also exists for AOCS.
This is introduced by GPDB commit ed364586b99. For AO/AOCS partition tables, it's possible to update across partitions. And it does have deleteDesc and uniqueCheckDesc if there were. The DeleteDesc and InsertDesc are not enough to decide if the partition has a update operation or not. Some partitions have visimap but some not, clean them if possible.
Authored-by: Zhang Mingli avamingli@gmail.com
fix #ISSUE_Number
Change logs
Describe your change clearly, including what problem is being solved or what feature is being added.
If it has some breaking backward or forward compatibility, please clary.
Why are the changes needed?
Describe why the changes are necessary.
Does this PR introduce any user-facing change?
If yes, please clarify the previous behavior and the change this PR proposes.
How was this patch tested?
Please detail how the changes were tested, including manual tests and any relevant unit or integration tests.
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🥳