Truncate CI tables on Main and Main tables on CI now we've decomposed
Now that we've decomposed we can get even more performance gains if we truncate the orphaned tables.
Some considerations:
- Locking may be tricky if there are cron jobs, prometheus exporters or autovacuums running on the tables
- Having absolute confidence nothing is reading the tables and/or a rollback strategy would be ideal in case we missed something
- One example discussed was moving them to a different schema before truncation. Foreign keys may be tricky in such a case
Change requests for initial truncation of some tables:
Change requests for the truncation of the rest of the tables:
- Staging: gitlab-com/gl-infra/production#7585 (closed)
- Production: gitlab-com/gl-infra/production#7770 (closed)
Edited by Omar Qunsul