2 Commits

Author	SHA1	Message	Date
Sean McGivern	d3d9077830	Add a helper to rename a column using a background migration ... This works the same way as change_column_type_using_background_migration, but for renaming a column. It takes a table, not a relation, to match its concurrent counterpart. Also, generalise the cleanup migrations to reduce code duplication.	2018-06-26 13:54:52 +01:00
Yorick Peterse	78d22fb20d	Use a background migration for issues.closed_at ... 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.	2018-01-03 12:28:00 +01:00