Fix 'Caught unhandled unknown exception; terminating' bug in SQL steps #5
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.
Running pgagent on Debian jessie with an SQL jobstep crashes the worker thread with the error message
Caught unhandled unknown exception; terminating
. Both job and jobstep status then remain asr
(running) until the pgagent process quits. After restarting pgagent, which cleans up the job status and sets it tod
(aborted), the job containing the SQL jobstep is free to run again, but the next run will end up in the same deadlock situation.I have tracked down the problem to
DBconn::GetLastError()
, which gets called after each SQL jobstep execution inJob::Execute()
: there,DBconn::GetLastError()
throws an exception whenever the last error message is empty.This pull request fixes this problem by adding missing bounds checks to
DBconn::GetLastError()
.Here is a log of pgagent with an SQL jobstep: