diff options
| author | Yorick Peterse <yorickpeterse@gmail.com> | 2017-12-21 16:44:07 +0100 |
|---|---|---|
| committer | Yorick Peterse <yorickpeterse@gmail.com> | 2018-01-03 12:28:00 +0100 |
| commit | 78d22fb20db14c90861318b9f316466fbf002114 (patch) | |
| tree | 9ac0e16582926c812f56830eab74ea970caea2ac /db/schema.rb | |
| parent | 1dac4271798a3b9ad36c3d985a3f7740cd1c60b3 (diff) | |
| download | gitlab-ce-78d22fb20db14c90861318b9f316466fbf002114.tar.gz | |
Use a background migration for issues.closed_atchange-issues-closed-at-background-migration
In a previous attempt (rolled back in
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/16021) we tried
to migrate `issues.closed_at` from timestamp to timestamptz using a
regular migration. This has a bad impact on GitLab.com and as such was
rolled back.
This commit re-implements the original migrations using generic
background migrations, allowing us to still migrate the data in a single
release but without a negative impact on availability.
To ensure the database schema is up to date the background migrations
are performed inline in development and test environments. We also make
sure to not migrate that that doesn't need migrating in the first place
or has already been migrated.
Diffstat (limited to 'db/schema.rb')
| -rw-r--r-- | db/schema.rb | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/db/schema.rb b/db/schema.rb index 42715d5e1e8..cd1f5d12fef 100644 --- a/db/schema.rb +++ b/db/schema.rb @@ -11,7 +11,7 @@ # # It's strongly recommended that you check this file into your version control system. -ActiveRecord::Schema.define(version: 20171220191323) do +ActiveRecord::Schema.define(version: 20171221140220) do # These are extensions that must be enabled in order to support this database enable_extension "plpgsql" |