Enable `ensure_lfs_object_project_uniqueness` FF by default
What does this MR do and why?
This MR enables the ensure_lfs_object_project_uniqueness
FF by default. The feature introduced uses an explicit locking mechanism (advisory lock) in the lfs_object_project
model, executed on every record creation. A new callback will take this advisory lock and affect the 3 column values (lfs_object_id
, project_id
, and repository_type
) if they are present.
We want to deduplicate the lfs_objects_projects
table by lfs_object_id
, project_id
, and repository_type
. To achieve this, we have !154323 (merged), which creates a batched background migration. However, during the deduplication, we should also avoid creating new duplicates in the lfs_objects_projects
table.
The monitoring process can be found in #472750 (closed) and !159264 (comment 2032352722)
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Related to #472750 (closed)