1. 04 May, 2018 1 commit
  2. 01 May, 2018 1 commit
  3. 24 Apr, 2018 5 commits
  4. 06 Apr, 2018 1 commit
  5. 05 Apr, 2018 1 commit
  6. 29 Mar, 2018 1 commit
  7. 09 Mar, 2018 1 commit
  8. 28 Feb, 2018 3 commits
  9. 21 Feb, 2018 1 commit
  10. 20 Feb, 2018 1 commit
  11. 16 Feb, 2018 2 commits
  12. 15 Feb, 2018 1 commit
  13. 14 Feb, 2018 2 commits
  14. 12 Feb, 2018 2 commits
  15. 08 Feb, 2018 1 commit
  16. 01 Feb, 2018 1 commit
  17. 31 Jan, 2018 1 commit
  18. 18 Jan, 2018 1 commit
    • Yorick Peterse's avatar
      Reduce UPDATEs for background column type changes · 361e958dd8e1
      Yorick Peterse authored
      Prior to this commit we would essentially update all rows in a table,
      even those where the source column (e.g. `issues.closed_at`) was NULL.
      This in turn could lead to statement timeouts when using the default
      batch size of 10 000 rows per job.
      
      To work around this we don't schedule jobs for rows where the source
      value is NULL. We also don't update rows where the source column is NULL
      (as an extra precaution) or the target column already has a non-NULL
      value. Using this approach it should be possible to update 10 000 rows
      in the "issues" table in about 7.5 - 8 seconds.
      
      Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/42158
      361e958dd8e1
  19. 12 Jan, 2018 1 commit
  20. 10 Jan, 2018 1 commit
    • Jan Provaznik's avatar
      Denormalize commits count for merge request diffs · fc52079e6da2
      Jan Provaznik authored
      For each MR diff an extra 'SELECT COUNT()' is executed
      to get number of commits for the diff. Overall time to get counts for
      all MR diffs may be quite expensive. To speed up loading of MR info,
      information about number of commits is stored in a MR diff's extra column.
      
      Closes #38068
      fc52079e6da2
  21. 06 Jan, 2018 4 commits
  22. 04 Jan, 2018 1 commit
    • Stan Hu's avatar
      Avoid leaving a push event empty if payload cannot be created · ca262b74f4af
      Stan Hu authored
      If the payload cannot be created for some reason, we could be left with a nil
      push event payload, which causes Error 500s when viewing the dashboard. Guard
      against this error and log when it happens.
      
      Avoids problems seen in #38823
      ca262b74f4af
  23. 03 Jan, 2018 2 commits
    • Michael Kozono's avatar
      Make DeleteConflictingRedirectRoutes no-op · e76333633355
      Michael Kozono authored
      Both the post-deploy and background migration.
      e76333633355
    • Yorick Peterse's avatar
      Use a background migration for issues.closed_at · 7e47dfe70d60
      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.
      7e47dfe70d60
  24. 02 Jan, 2018 1 commit
  25. 05 Dec, 2017 1 commit
  26. 04 Dec, 2017 1 commit
    • Michael Kozono's avatar
      Follow symlinks · cfb73634caa4
      Michael Kozono authored
      In particular, the Omnibus uploads directory is generally a symlink.
      cfb73634caa4
  27. 01 Dec, 2017 1 commit