News for hackers. Stuff that matters.

A comment on GitLab Database Incident – Live Report.

Re:GitLab Database Incident – Live Report by umbrai_nation on Tuesday January 31, 2017 @10:39PM (#13538020)
"Of around 310 GB only about 4.5 GB is left"

What is gitlab storing in their database? From what I understand, the repos were untouched by the DB problems, so what is taking up a third of a terabyte of DB space?

[ Parent | on HN ]
Re:GitLab Database Incident – Live Report by YorickPeterse on Wednesday February 01, 2017 @06:38AM (#13539909)
issues, merge requests (titles, descriptions, etc), comments, events ("X pushed to Y"), labels, projects, milestones, users, permissions, project statistics, CI builds information, abuse reports, the list goes on.
[ Parent | on HN ]
Re:GitLab Database Incident – Live Report by X-Istence on Tuesday January 31, 2017 @11:13PM (#13538174)
Tickets, tags, labels, users information/data and more. Sounds like they also host snippets out of the PostgreSQL database.

310 GB for a database is not all that large.

[ Parent | on HN ]
Re:GitLab Database Incident – Live Report by neandrake on Tuesday January 31, 2017 @11:30PM (#13538249)
The database might have tables for commit data so history etc. can be searched, and possibly used for managing on-server operations like merges etc.
[ Parent | on HN ]