-
Notifications
You must be signed in to change notification settings - Fork 848
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
Do not clobber the baserel cache on UDF error #4890
Conversation
Codecov Report
@@ Coverage Diff @@
## main #4890 +/- ##
==========================================
+ Coverage 89.46% 89.59% +0.12%
==========================================
Files 225 225
Lines 50288 50146 -142
==========================================
- Hits 44992 44928 -64
+ Misses 5296 5218 -78
Continue to review full report at Codecov.
|
/* | ||
* Volatile is needed because these are the local variables that are | ||
* modified between setjmp/longjmp calls. | ||
*/ | ||
volatile bool reset_fetcher_type = false; | ||
volatile bool reset_baserel_info = false; |
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.
So that's what the -Wclobbered
warning was about... I'll fix the other places separately.
The baserel cache should only be allocated and freed by the top-level query.
The one in job_stat.c could probably lead to errors.
Backports should also include this commit to remove the accidental debug output: 9964ba8 |
The baserel cache should only be allocated and freed by the top-level query.
Also enable and fix -Wclobbered which could have prevented this error.
Fixes #4823
Disable-check: commit-count