1ab33b15d1
remove_column should only be used in the up (or change) step of a migration if it's a post-deployment migration. Otherwise there will be downtime due to the ActiveRecord column cache, which we can avoid by using the IgnorableColumn concern in combination with a post-deployment migration.
21 lines
597 B
Ruby
21 lines
597 B
Ruby
# rubocop:disable Migration/RemoveColumn
|
|
# See http://doc.gitlab.com/ce/development/migration_style_guide.html
|
|
# for more information on how to write migrations for GitLab.
|
|
|
|
# rubocop:disable Migration/UpdateLargeTable
|
|
class RemoveProjectsPushesSinceGc < ActiveRecord::Migration
|
|
include Gitlab::Database::MigrationHelpers
|
|
|
|
DOWNTIME = true
|
|
DOWNTIME_REASON = 'This migration removes an existing column'
|
|
|
|
disable_ddl_transaction!
|
|
|
|
def up
|
|
remove_column :projects, :pushes_since_gc
|
|
end
|
|
|
|
def down
|
|
add_column_with_default :projects, :pushes_since_gc, :integer, default: 0
|
|
end
|
|
end
|