Skip to content

Remove unused index for confidence level migrations

Can Eldem requested to merge drop-unused-confidence-index into master

What does this MR do?

Drop index for post migrations in vulnerabilities and vulnerability_occurrences table.

Related issue: #217116 (closed)

Output of migrations


Up

gdk-ee/gitlab [drop-unused-confidence-index●] » rails db:migrate:down VERSION=20200527094322
== 20200527094322 DropVulnerabilityConfidenceIndex: reverting =================
-- transaction_open?()
   -> 0.0000s
-- index_exists?(:vulnerabilities, :id, {:where=>"confidence = 0", :name=>"index_vulnerability_on_id_and_confidence_eq_zero", :algorithm=>:concurrently})
   -> 0.0051s
-- add_index(:vulnerabilities, :id, {:where=>"confidence = 0", :name=>"index_vulnerability_on_id_and_confidence_eq_zero", :algorithm=>:concurrently})
   -> 0.0061s
== 20200527094322 DropVulnerabilityConfidenceIndex: reverted (0.0116s) ========


Down

gdk-ee/gitlab [drop-unused-confidence-index●] » rails db:migrate:up VERSION=20200527094322
== 20200527094322 DropVulnerabilityConfidenceIndex: migrating =================
-- transaction_open?()
   -> 0.0000s
-- indexes(:vulnerabilities)
   -> 0.0053s
-- remove_index(:vulnerabilities, {:algorithm=>:concurrently, :name=>"index_vulnerability_on_id_and_confidence_eq_zero"})
   -> 0.0021s
== 20200527094322 DropVulnerabilityConfidenceIndex: migrated (0.0078s) ========


Up 

gdk-ee/gitlab [drop-unused-confidence-index●] » rails db:migrate:up VERSION=20200527095401
== 20200527095401 DropVulnerabilityOccurrenceConfidenceIndex: migrating =======
-- transaction_open?()
   -> 0.0000s
-- indexes(:vulnerability_occurrences)
   -> 0.0039s
-- remove_index(:vulnerability_occurrences, {:algorithm=>:concurrently, :name=>"index_vulnerability_occurrences_on_id_and_confidence_eq_zero"})
   -> 0.0026s
== 20200527095401 DropVulnerabilityOccurrenceConfidenceIndex: migrated (0.0069s)

Down

gdk-ee/gitlab [drop-unused-confidence-index●] » rails db:migrate:down VERSION=20200527095401
== 20200527095401 DropVulnerabilityOccurrenceConfidenceIndex: reverting =======
-- transaction_open?()
   -> 0.0000s
-- index_exists?(:vulnerability_occurrences, :id, {:where=>"confidence = 0", :name=>"index_vulnerability_occurrences_on_id_and_confidence_eq_zero", :algorithm=>:concurrently})
   -> 0.0034s
-- add_index(:vulnerability_occurrences, :id, {:where=>"confidence = 0", :name=>"index_vulnerability_occurrences_on_id_and_confidence_eq_zero", :algorithm=>:concurrently})
   -> 0.0040s
== 20200527095401 DropVulnerabilityOccurrenceConfidenceIndex: reverted (0.0078s)

Does this MR meet the acceptance criteria?

Conformity

Edited by Can Eldem

Merge request reports