-
Notifications
You must be signed in to change notification settings - Fork 48
RHINENG-29746: backport notified #2337
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
Merged
+90
−1
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
14 changes: 14 additions & 0 deletions
14
database_admin/migrations/168_backport_advisories_notified.down.sql
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,14 @@ | ||
| CREATE OR REPLACE FUNCTION backfill_account_advisory(rh_account_id_in INTEGER) | ||
| RETURNS VOID AS | ||
| $backfill$ | ||
| BEGIN | ||
| PERFORM refresh_account_advisory_caches_multi(NULL, rh_account_id_in); | ||
| END; | ||
| $backfill$ LANGUAGE plpgsql; | ||
|
|
||
| SELECT drop_table_partition_triggers('account_advisory_sync_notified_insert', | ||
| $$BEFORE INSERT$$, | ||
| 'account_advisory', | ||
| $$FOR EACH ROW EXECUTE PROCEDURE sync_account_advisory_notified_on_insert()$$); | ||
|
|
||
| DROP FUNCTION IF EXISTS sync_account_advisory_notified_on_insert(); |
37 changes: 37 additions & 0 deletions
37
database_admin/migrations/168_backport_advisories_notified.up.sql
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,37 @@ | ||
| CREATE OR REPLACE FUNCTION backfill_account_advisory(rh_account_id_in INTEGER) | ||
| RETURNS VOID AS | ||
| $backfill$ | ||
| BEGIN | ||
| PERFORM refresh_account_advisory_caches_multi(NULL, rh_account_id_in); | ||
|
|
||
| -- copy `notified` for all `workspace_id`s per account | ||
| UPDATE account_advisory aa | ||
| SET notified = aad.notified | ||
| FROM advisory_account_data aad | ||
| WHERE aa.advisory_id = aad.advisory_id | ||
| AND aa.rh_account_id = aad.rh_account_id | ||
| AND aa.rh_account_id = rh_account_id_in | ||
| AND aad.notified IS NOT NULL; | ||
| END; | ||
| $backfill$ LANGUAGE plpgsql; | ||
|
|
||
| CREATE OR REPLACE FUNCTION sync_account_advisory_notified_on_insert() | ||
| RETURNS TRIGGER AS | ||
| $sync_notified_insert$ | ||
| BEGIN | ||
| IF NEW.notified IS NULL THEN | ||
| SELECT notified INTO NEW.notified | ||
| FROM account_advisory | ||
| WHERE rh_account_id = NEW.rh_account_id | ||
| AND advisory_id = NEW.advisory_id | ||
| AND notified IS NOT NULL | ||
| LIMIT 1; | ||
| END IF; | ||
| RETURN NEW; | ||
| END; | ||
| $sync_notified_insert$ LANGUAGE plpgsql; | ||
|
|
||
| SELECT create_table_partition_triggers('account_advisory_sync_notified_insert', | ||
| $$BEFORE INSERT$$, | ||
| 'account_advisory', | ||
| $$FOR EACH ROW EXECUTE PROCEDURE sync_account_advisory_notified_on_insert()$$); | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
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.
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.
issue (bug_risk): A concurrent workspace insert can permanently retain a NULL
notifiedvalue: the trigger reads existingaccount_advisoryrows before the notification transaction updates them, while the notification UPDATE can finish before the new insert commits. The new row then remains unnotified even thoughadvisory_account_data.notifiedand the existing workspace rows are set.Triggers: When a new workspace for an already-notified advisory is inserted concurrently with
markAdvisoriesNotified.Suggested fix: Synchronize the insert and notification update with a locking or atomic database operation, or derive the inserted value from
advisory_account_data.notifiedas well as existingaccount_advisoryrows.