<!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION --> *This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.* <!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION --> GitLab.com's Postgres database is growing and we've reached about 13 TB as of May 2021. T This epic is meant to facilitate coordinating and identifying approaches to achieve two points: 1. Reduce the total size (in many cases a one-time win) 1. Reduce the database growth rate The epic is also meant to act as a source for explaining sources of database growth. Per-table statistics (physical size, row count estimates) can be found in this [sheet](https://docs.google.com/spreadsheets/d/1hOP62fZJFJdOyC1dzmT4DeF4xU2qsm3TzReHIquMMZI/edit#gid=1224268488). Database storage growth over time can be observed in [Grafana](https://dashboards.gitlab.net/d/000000144/postgresql-overview?viewPanel=10&from=now-30d&orgId=1&to=now). Many new issues have been discovered and added to this epic as a part of the ongoing [Sharding - Database Scalability](https://gitlab.com/groups/gitlab-org/-/epics/5759) initiative.