When dispatching command to segments, if the 'cancelOnError' is true and the query is being canceled, it will bail out.
But before this pr, it check the 'InterruptPending' to see if there is a cancel request. When the process got a singal, like customer signal, not a query cancel request, it will cancle the query too.
So I use the QueryCancelPending instead of InterrupPending here.
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).
When dispatching command to segments, if the 'cancelOnError' is true and the query is being canceled, it will bail out. But before this pr, it check the 'InterruptPending' to see if there is a cancel request. When the process got a singal, like customer signal, not a query cancel request, it will cancle the query too.
So I use the QueryCancelPending instead of InterrupPending here.
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🥳