Remove pipeline_security duplicated indexes
After #385701 (closed), we can identify duplicated indexes. At the moment, there are many duplicate indexes that can be removed from our database, as they are not needed anymore.
The list of duplicated indexes can be found in the duplicate_indexes.yml
file.
We have identified the following duplicated indexes owned by grouppipeline security:
ci_job_artifacts table
- index_ci_job_artifacts_on_id_project_id_and_created_at:
index_ci_job_artifacts_on_project_id
- index_ci_job_artifacts_on_id_project_id_and_file_type:
index_ci_job_artifacts_on_project_id
- index_ci_job_artifacts_on_project_id_and_id:
index_ci_job_artifacts_on_project_id
ci_pipeline_artifacts table
- index_ci_pipeline_artifacts_on_pipeline_id_and_file_type:
index_ci_pipeline_artifacts_on_pipeline_id
NOTE: Consider removing indexes showed on the right. Indexes at the left are covering for the duplicated one.
Feel free to split this issue into several under &11436 (closed) if that aligns more with how your group works.
See the references below to remove indexes. If the table is larger or with a lot of traffic, please consider dropping the index asynchronously.
References:
- https://docs.gitlab.com/ee/development/database/adding_database_indexes.html#drop-indexes-asynchronously
- https://docs.gitlab.com/ee/development/migration_style_guide.html#removing-indexes
Related #423983 (closed)
Edited by Leonardo da Rosa