Add migrations for missing merge_requests stage 2 indexes for bigint
What does this MR do and why?
Users are reporting issue raised during bigint migration, Upgrade from 18.7.1 to 18.8.0 fails in DB migra... (#586512 - closed)
The root cause would be, some existing indexes from merge_requests table are not present in DB (user DB derived from schema). When we swap bigint indexes, exception raised as those normal indexes do not exist.
In this MR, we add one more migration before the migration for swapping stage 2 bigint columns, so any missing indexes will be picked up. The timestamp in this MR, 20260102015627,is right before the swapping stage 2 bigint columns 20260102015629.
References
- Issue - Upgrade from 18.7.1 to 18.8.0 fails in DB migra... (#586512 - closed)
- Previous similar MR for stage 1 - Add migrations for misisng merge_requests index... (!215161 - merged)
Screenshots or screen recordings
NA
How to set up and validate locally
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.