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.
25 lines
914 B
Ruby
25 lines
914 B
Ruby
# rubocop:disable Migration/RemoveColumn
|
|
class MigrateProjectStatistics < ActiveRecord::Migration
|
|
include Gitlab::Database::MigrationHelpers
|
|
|
|
DOWNTIME = true
|
|
DOWNTIME_REASON = 'Removes two columns from the projects table'
|
|
|
|
def up
|
|
# convert repository_size in float (megabytes) to integer (bytes),
|
|
# initialize total storage_size with repository_size
|
|
execute <<-EOF
|
|
INSERT INTO project_statistics (project_id, namespace_id, commit_count, storage_size, repository_size)
|
|
SELECT id, namespace_id, commit_count, (repository_size * 1024 * 1024), (repository_size * 1024 * 1024) FROM projects
|
|
EOF
|
|
|
|
remove_column :projects, :repository_size
|
|
remove_column :projects, :commit_count
|
|
end
|
|
|
|
# rubocop: disable Migration/AddColumn
|
|
def down
|
|
add_column :projects, :repository_size, :float, default: 0.0
|
|
add_column :projects, :commit_count, :integer, default: 0
|
|
end
|
|
end
|