Read about our upcoming Code of Conduct on this issue

  1. 06 Jul, 2017 1 commit
    • Yorick Peterse's avatar
      Add many foreign keys to the projects table · 8b8987deee58
      Yorick Peterse authored
      This removes the need for relying on Rails' "dependent" option for data
      removal, which is _incredibly_ slow (even when using :delete_all) when
      deleting large amounts of data. This also ensures data consistency is
      enforced on DB level and not on application level (something Rails is
      really bad at).
      
      This commit also includes various migrations to add foreign keys to
      tables that eventually point to "projects" to ensure no rows get
      orphaned upon removing a project.
      8b8987deee58
  2. 05 Jul, 2017 1 commit
  3. 21 Jun, 2017 1 commit
  4. 16 Jun, 2017 2 commits
  5. 02 Jun, 2017 1 commit
  6. 13 May, 2017 1 commit
  7. 12 May, 2017 1 commit
  8. 04 May, 2017 2 commits
  9. 21 Apr, 2017 1 commit
  10. 10 Apr, 2017 2 commits
  11. 06 Apr, 2017 1 commit
  12. 05 Apr, 2017 1 commit
  13. 04 Apr, 2017 1 commit
  14. 21 Mar, 2017 1 commit
  15. 17 Mar, 2017 1 commit
  16. 14 Mar, 2017 2 commits
  17. 23 Feb, 2017 1 commit
  18. 17 Feb, 2017 1 commit
  19. 27 Jan, 2017 3 commits
  20. 03 Jan, 2017 1 commit
  21. 20 Dec, 2016 1 commit
  22. 15 Dec, 2016 1 commit
  23. 02 Dec, 2016 1 commit
  24. 23 Nov, 2016 2 commits
    • Yorick Peterse's avatar
      Remove event caching code · 0b3b7320a525
      Yorick Peterse authored
      Flushing the events cache worked by updating a recent number of rows in
      the "events" table. This has the result that on PostgreSQL a lot of dead
      tuples are produced on a regular basis. This in turn means that
      PostgreSQL will spend considerable amounts of time vacuuming this table.
      This in turn can lead to an increase of database load.
      
      For GitLab.com we measured the impact of not using events caching and
      found no measurable increase in response timings. Meanwhile not flushing
      the events cache lead to the "events" table having no more dead tuples
      as now rows are only inserted into this table.
      
      As a result of this we are hereby removing events caching as it does not
      appear to help and only increases database load.
      
      For more information see the following comment:
      https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/6578#note_18864037
      0b3b7320a525
    • Ahmad Sherif's avatar
      Drop Project#authorized_for_user? in favor of ProjectTeam#member? · 51d69a1315b6
      Ahmad Sherif authored
      Closes #23938
      51d69a1315b6
  25. 17 Nov, 2016 1 commit
  26. 14 Nov, 2016 1 commit
  27. 09 Nov, 2016 1 commit
  28. 28 Oct, 2016 1 commit
  29. 20 Oct, 2016 1 commit
  30. 19 Oct, 2016 2 commits
  31. 07 Oct, 2016 1 commit
  32. 20 Sep, 2016 1 commit