refactor: using only update_message_processing_status
to change status
#201
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.
Description
This PR adds a small refactor to use
update_message_processing_status
helper function to change the message status instead of manually running the SQL.This is useful for tracking metrics inside the
update_message_processing_status
function and following the DRY.update_message_processing_status only to change status
to be used with PgPool and Pg transactions,Resolves #189
How Has This Been Tested?
Just a build-and-up local smoke test.
Due Diligence