0fc9f9d3e7
DB schema generated by a migration may look different in rails 4 and 5 (because rails 5 may use different default values). For this reason it's important to explicitly set for which rails version a migration was written for. See https://stackoverflow.com/questions/35929869/activerecordmigration-deprecation-warning-asks-for-rails-version-but-im-no/35930912#35930912
23 lines
856 B
Ruby
23 lines
856 B
Ruby
# See http://doc.gitlab.com/ce/development/migration_style_guide.html
|
|
# for more information on how to write migrations for GitLab.
|
|
|
|
class OptimizeCiJobArtifacts < ActiveRecord::Migration[4.2]
|
|
include Gitlab::Database::MigrationHelpers
|
|
|
|
# Set this constant to true if this migration requires downtime.
|
|
DOWNTIME = false
|
|
|
|
disable_ddl_transaction!
|
|
|
|
def up
|
|
# job_id is just here to be a covering index for index only scans
|
|
# since we'll almost always be joining against ci_builds on job_id
|
|
add_concurrent_index(:ci_job_artifacts, [:expire_at, :job_id])
|
|
add_concurrent_index(:ci_builds, [:artifacts_expire_at], where: "artifacts_file <> ''")
|
|
end
|
|
|
|
def down
|
|
remove_concurrent_index(:ci_job_artifacts, [:expire_at, :job_id])
|
|
remove_concurrent_index(:ci_builds, [:artifacts_expire_at], where: "artifacts_file <> ''")
|
|
end
|
|
end
|