Skip to content

Draft: Backfill partitioned merge_request_diff_commits

Matt Kasa requested to merge mattkasa/backfill_mrdiffcommits_partitions into master

What does this MR do and why?

Backfill partitioned merge_request_diff_commits

⚠️ This is MR3 in Add sharding key to merge_request_diff_commits ... (#501473) and should not be merged before MR1 and MR2 ⚠️

Related to #422766

Migration output

Up 
main: == [advisory_lock_connection] object_id: 118900, pg_backend_pid: 76194
main: == 20241031153140 QueueBackfillPartitionedMergeRequestDiffCommits: migrating ==
main: == 20241031153140 QueueBackfillPartitionedMergeRequestDiffCommits: migrated (0.0455s) 

main: == [advisory_lock_connection] object_id: 118900, pg_backend_pid: 76194
ci: == [advisory_lock_connection] object_id: 129400, pg_backend_pid: 76196
ci: == 20241031153140 QueueBackfillPartitionedMergeRequestDiffCommits: migrating ==
ci: -- The migration is skipped since it modifies the schemas: [:gitlab_main].
ci: -- This database can only apply migrations in one of the following schemas: [:gitlab_ci, :gitlab_internal, :gitlab_shared].
ci: == 20241031153140 QueueBackfillPartitionedMergeRequestDiffCommits: migrated (0.0070s) 

ci: == [advisory_lock_connection] object_id: 129400, pg_backend_pid: 76196

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.

Edited by Matt Kasa

Merge request reports