Select candidate for pg_repack disk size reduction on CI database
In order to reclaim disk space on CI, we evaluate impact and gain.
We need to select 1 to 3 candidates to execute pg_repack on.
Metrics
- Low impact on GitLab.com performance
- High expected storage reduction
Acceptance criteria
-
Have a list of 1 to 3 (sub) tables to run pg_repackon
List
-
group_type_ci_runner_machines, size 8 GiB, estimated table bloat ~97% -
gitlab_partitions_dynamic.ci_runner_machine_builds_100, size 14 GiB, estimated table bloat ~71%
Edited by Alexander Sosna