1. 03 Jan, 2018 1 commit
    • Yorick Peterse's avatar
      Use a background migration for issues.closed_at · 78d22fb2
      Yorick Peterse authored
      In a previous attempt (rolled back in
      https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/16021) we tried
      to migrate `issues.closed_at` from timestamp to timestamptz using a
      regular migration. This has a bad impact on GitLab.com and as such was
      rolled back.
      
      This commit re-implements the original migrations using generic
      background migrations, allowing us to still migrate the data in a single
      release but without a negative impact on availability.
      
      To ensure the database schema is up to date the background migrations
      are performed inline in development and test environments. We also make
      sure to not migrate that that doesn't need migrating in the first place
      or has already been migrated.
      78d22fb2
  2. 02 Jan, 2018 19 commits
  3. 01 Jan, 2018 4 commits
  4. 30 Dec, 2017 1 commit
  5. 29 Dec, 2017 9 commits
  6. 28 Dec, 2017 6 commits