Fix concurrency issue with migration for user_interacted_projects table.
What does this MR do?
The concurrency issue originates from inserts on
user_interacted_projects
from the app while running the post-deploy
migration.
This change comes with a strategy to lock the table while removing duplicates and creating the unique index (and similar for FK constraints).
Also, we'll have a non-unique index until the post-deploy migration is finished to speed up queries during that time.
Does this MR meet the acceptance criteria?
- Review
-
Has been reviewed by Backend -
Has been reviewed by Database
-
-
End-to-end tests pass ( package-qa
manual pipeline job)
What are the relevant issue numbers?
Edited by Yorick Peterse