-
Dylan Griffith authored
This migration was added in !65201 which was in 14.3. As such this migration must have already been run before upgrading to this version of GitLab. We cannot remove or no-op this migration since it makes schema changes but we remove the explicit `LOCK` statements which were only there for performance reasons. The migration works fine and updates the schema the same without them. They only served to reduce the risk of lock timeouts on busy tables.
487c2c2cDylan Griffith authoredThis migration was added in !65201 which was in 14.3. As such this migration must have already been run before upgrading to this version of GitLab. We cannot remove or no-op this migration since it makes schema changes but we remove the explicit `LOCK` statements which were only there for performance reasons. The migration works fine and updates the schema the same without them. They only served to reduce the risk of lock timeouts on busy tables.
Loading