Catch unsafe migrations in development
✓ Detects potentially dangerous operations
✓ Prevents them from running by default
✓ Provides instructions on safer ways to do what you want
Supports PostgreSQL, MySQL, and MariaDB
🍊 Battle-tested at Instacart
Add this line to your application’s Gemfile:
gem "strong_migrations"And run:
bundle install
rails generate strong_migrations:installStrong Migrations sets a long statement timeout for migrations so you can set a short statement timeout for your application.
When you run a migration that’s potentially dangerous, you’ll see an error message like:
=== Dangerous operation detected #strong_migrations ===
Active Record caches attributes, which causes problems
when removing columns. Be sure to ignore the column:
class User < ApplicationRecord
self.ignored_columns += ["name"]
end
Deploy the code, then wrap this step in a safety_assured { ... } block.
class RemoveColumn < ActiveRecord::Migration[7.1]
def change
safety_assured { remove_column :users, :name }
end
endAn operation is classified as dangerous if it either:
- Blocks reads or writes for more than a few seconds (after a lock is acquired)
- Has a good chance of causing application errors
Potentially dangerous operations:
- removing a column
- changing the type of a column
- renaming a column
- renaming a table
- creating a table with the force option
- adding an auto-incrementing column
- adding a stored generated column
- adding a check constraint
- executing SQL directly
- backfilling data
Postgres-specific checks:
- adding an index non-concurrently
- adding a reference
- adding a foreign key
- adding a unique constraint
- adding an exclusion constraint
- adding a json column
- setting NOT NULL on an existing column
- adding a column with a default value
Config-specific checks:
Best practices:
You can also add custom checks or disable specific checks.
Active Record caches database columns at runtime, so if you drop a column, it can cause exceptions until your app reboots.
class RemoveSomeColumnFromUsers < ActiveRecord::Migration[7.1]
def change
remove_column :users, :some_column
end
end- Tell Active Record to ignore the column from its cache
class User < ApplicationRecord
self.ignored_columns += ["some_column"]
end- Deploy the code
- Write a migration to remove the column (wrap in
safety_assuredblock)
class RemoveSomeColumnFromUsers < ActiveRecord::Migration[7.1]
def change
safety_assured { remove_column :users, :some_column }
end
end- Deploy and run the migration
- Remove the line added in step 1
Changing the type of a column causes the entire table to be rewritten. During this time, reads and writes are blocked in Postgres, and writes are blocked in MySQL and MariaDB.
class ChangeSomeColumnType < ActiveRecord::Migration[7.1]
def change
change_column :users, :some_column, :new_type
end
endSome changes don’t require a table rewrite and are safe in Postgres:
| Type | Safe Changes |
|---|---|
cidr |
Changing to inet |
citext |
Changing to text if not indexed, changing to string with no :limit if not indexed |
datetime |
Increasing or removing :precision, changing to timestamptz when session time zone is UTC in Postgres 12+ |
decimal |
Increasing :precision at same :scale, removing :precision and :scale |
interval |
Increasing or removing :precision |
numeric |
Increasing :precision at same :scale, removing :precision and :scale |
string |
Increasing or removing :limit, changing to text, changing citext if not indexed |
text |
Changing to string with no :limit, changing to citext if not indexed |
time |
Increasing or removing :precision |
timestamptz |
Increasing or removing :limit, changing to datetime when session time zone is UTC in Postgres 12+ |
And some in MySQL and MariaDB:
| Type | Safe Changes |
|---|---|
string |
Increasing :limit from under 63 up to 63, increasing :limit from over 63 to the max (the threshold can be different if using an encoding other than utf8mb4 - for instance, it’s 85 for utf8mb3 and 255 for latin1) |
A safer approach is to:
- Create a new column
- Write to both columns
- Backfill data from the old column to the new column
- Move reads from the old column to the new column
- Stop writing to the old column
- Drop the old column
Renaming a column that’s in use will cause errors in your application.
class RenameSomeColumn < ActiveRecord::Migration[7.1]
def change
rename_column :users, :some_column, :new_name
end
endA safer approach is to:
- Create a new column
- Write to both columns
- Backfill data from the old column to the new column
- Move reads from the old column to the new column
- Stop writing to the old column
- Drop the old column
Renaming a table that’s in use will cause errors in your application.
class RenameUsersToCustomers < ActiveRecord::Migration[7.1]
def change
rename_table :users, :customers
end
endA safer approach is to:
- Create a new table
- Write to both tables
- Backfill data from the old table to the new table
- Move reads from the old table to the new table
- Stop writing to the old table
- Drop the old table
The force option can drop an existing table.
class CreateUsers < ActiveRecord::Migration[7.1]
def change
create_table :users, force: true do |t|
# ...
end
end
endCreate tables without the force option.
class CreateUsers < ActiveRecord::Migration[7.1]
def change
create_table :users do |t|
# ...
end
end
endIf you intend to drop an existing table, run drop_table first.
Adding an auto-incrementing column (serial/bigserial in Postgres and AUTO_INCREMENT in MySQL and MariaDB) causes the entire table to be rewritten. During this time, reads and writes are blocked in Postgres, and writes are blocked in MySQL and MariaDB.
class AddIdToCitiesUsers < ActiveRecord::Migration[7.1]
def change
add_column :cities_users, :id, :primary_key
end
endWith MySQL and MariaDB, this can also generate different values on replicas if using statement-based replication.
Create a new table and migrate the data with the same steps as renaming a table.
Adding a stored generated column causes the entire table to be rewritten. During this time, reads and writes are blocked in Postgres, and writes are blocked in MySQL and MariaDB.
class AddSomeColumnToUsers < ActiveRecord::Migration[7.1]
def change
add_column :users, :some_column, :virtual, type: :string, as: "...", stored: true
end
endAdd a non-generated column and use callbacks or triggers instead (or a virtual generated column with MySQL and MariaDB).
🐢 Safe by default available
Adding a check constraint blocks reads and writes in Postgres and blocks writes in MySQL and MariaDB while every row is checked.
class AddCheckConstraint < ActiveRecord::Migration[7.1]
def change
add_check_constraint :users, "price > 0", name: "price_check"
end
endAdd the check constraint without validating existing rows:
class AddCheckConstraint < ActiveRecord::Migration[7.1]
def change
add_check_constraint :users, "price > 0", name: "price_check", validate: false
end
endThen validate them in a separate migration.
class ValidateCheckConstraint < ActiveRecord::Migration[7.1]
def change
validate_check_constraint :users, name: "price_check"
end
endLet us know if you have a safe way to do this (check constraints can be added with NOT ENFORCED, but enforcing blocks writes).
Strong Migrations can’t ensure safety for raw SQL statements. Make really sure that what you’re doing is safe, then use:
class ExecuteSQL < ActiveRecord::Migration[7.1]
def change
safety_assured { execute "..." }
end
endActive Record creates a transaction around each migration, and backfilling in the same transaction that alters a table keeps the table locked for the duration of the backfill.
class AddSomeColumnToUsers < ActiveRecord::Migration[7.1]
def change
add_column :users, :some_column, :text
User.update_all some_column: "default_value"
end
endAlso, running a single query to update data can cause issues for large tables.
There are three keys to backfilling safely: batching, throttling, and running it outside a transaction. Use the Rails console or a separate migration with disable_ddl_transaction!.
class BackfillSomeColumn < ActiveRecord::Migration[7.1]
disable_ddl_transaction!
def up
User.unscoped.in_batches do |relation|
relation.update_all some_column: "default_value"
sleep(0.01) # throttle
end
end
end🐢 Safe by default available
In Postgres, adding an index non-concurrently blocks writes.
class AddSomeIndexToUsers < ActiveRecord::Migration[7.1]
def change
add_index :users, :some_column
end
endAdd indexes concurrently.
class AddSomeIndexToUsers < ActiveRecord::Migration[7.1]
disable_ddl_transaction!
def change
add_index :users, :some_column, algorithm: :concurrently
end
endIf you forget disable_ddl_transaction!, the migration will fail. Also, note that indexes on new tables (those created in the same migration) don’t require this.
With gindex, you can generate an index migration instantly with:
rails g index table column🐢 Safe by default available
Rails adds an index non-concurrently to references by default, which blocks writes in Postgres.
class AddReferenceToUsers < ActiveRecord::Migration[7.1]
def change
add_reference :users, :city
end
endMake sure the index is added concurrently.
class AddReferenceToUsers < ActiveRecord::Migration[7.1]
disable_ddl_transaction!
def change
add_reference :users, :city, index: {algorithm: :concurrently}
end
end🐢 Safe by default available
In Postgres, adding a foreign key blocks writes on both tables.
class AddForeignKeyOnUsers < ActiveRecord::Migration[7.1]
def change
add_foreign_key :users, :orders
end
endor
class AddReferenceToUsers < ActiveRecord::Migration[7.1]
def change
add_reference :users, :order, foreign_key: true
end
endAdd the foreign key without validating existing rows:
class AddForeignKeyOnUsers < ActiveRecord::Migration[7.1]
def change
add_foreign_key :users, :orders, validate: false
end
endThen validate them in a separate migration.
class ValidateForeignKeyOnUsers < ActiveRecord::Migration[7.1]
def change
validate_foreign_key :users, :orders
end
endIn Postgres, adding a unique constraint creates a unique index, which blocks reads and writes.
class AddUniqueConstraint < ActiveRecord::Migration[7.1]
def change
add_unique_constraint :users, :some_column
end
endCreate a unique index concurrently, then use it for the constraint.
class AddUniqueConstraint < ActiveRecord::Migration[7.1]
disable_ddl_transaction!
def up
add_index :users, :some_column, unique: true, algorithm: :concurrently
add_unique_constraint :users, using_index: "index_users_on_some_column"
end
def down
remove_unique_constraint :users, :some_column
end
endIn Postgres, adding an exclusion constraint blocks reads and writes while every row is checked.
class AddExclusionConstraint < ActiveRecord::Migration[7.1]
def change
add_exclusion_constraint :users, "number WITH =", using: :gist
end
endLet us know if you have a safe way to do this (exclusion constraints cannot be marked NOT VALID).
In Postgres, there’s no equality operator for the json column type, which can cause errors for existing SELECT DISTINCT queries in your application.
class AddPropertiesToUsers < ActiveRecord::Migration[7.1]
def change
add_column :users, :properties, :json
end
endUse jsonb instead.
class AddPropertiesToUsers < ActiveRecord::Migration[7.1]
def change
add_column :users, :properties, :jsonb
end
end🐢 Safe by default available
In Postgres, setting NOT NULL on an existing column blocks reads and writes while every row is checked.
class SetSomeColumnNotNull < ActiveRecord::Migration[7.1]
def change
change_column_null :users, :some_column, false
end
endInstead, add a check constraint.
For Rails 6.1+, use:
class SetSomeColumnNotNull < ActiveRecord::Migration[7.1]
def change
add_check_constraint :users, "some_column IS NOT NULL", name: "users_some_column_null", validate: false
end
endFor Rails < 6.1, use:
class SetSomeColumnNotNull < ActiveRecord::Migration[6.0]
def change
safety_assured do
execute 'ALTER TABLE "users" ADD CONSTRAINT "users_some_column_null" CHECK ("some_column" IS NOT NULL) NOT VALID'
end
end
endThen validate it in a separate migration. A NOT NULL check constraint is functionally equivalent to setting NOT NULL on the column (but it won’t show up in schema.rb in Rails < 6.1). In Postgres 12+, once the check constraint is validated, you can safely set NOT NULL on the column and drop the check constraint.
For Rails 6.1+, use:
class ValidateSomeColumnNotNull < ActiveRecord::Migration[7.1]
def change
validate_check_constraint :users, name: "users_some_column_null"
# in Postgres 12+, you can then safely set NOT NULL on the column
change_column_null :users, :some_column, false
remove_check_constraint :users, name: "users_some_column_null"
end
endFor Rails < 6.1, use:
class ValidateSomeColumnNotNull < ActiveRecord::Migration[6.0]
def change
safety_assured do
execute 'ALTER TABLE "users" VALIDATE CONSTRAINT "users_some_column_null"'
end
# in Postgres 12+, you can then safely set NOT NULL on the column
change_column_null :users, :some_column, false
safety_assured do
execute 'ALTER TABLE "users" DROP CONSTRAINT "users_some_column_null"'
end
end
endIn earlier versions of Postgres, adding a column with a default value to an existing table causes the entire table to be rewritten. During this time, reads and writes are blocked in Postgres.
class AddSomeColumnToUsers < ActiveRecord::Migration[7.1]
def change
add_column :users, :some_column, :text, default: "default_value"
end
endIn Postgres 11+, this no longer requires a table rewrite and is safe (except for volatile functions like gen_random_uuid()).
Instead, add the column without a default value, then change the default.
class AddSomeColumnToUsers < ActiveRecord::Migration[7.1]
def up
add_column :users, :some_column, :text
change_column_default :users, :some_column, "default_value"
end
def down
remove_column :users, :some_column
end
endThen backfill the data.
Rails < 7 enables partial writes by default, which can cause incorrect values to be inserted when changing the default value of a column.
class ChangeSomeColumnDefault < ActiveRecord::Migration[6.1]
def change
change_column_default :users, :some_column, from: "old", to: "new"
end
end
User.create!(some_column: "old") # can insert "new"Disable partial writes in config/application.rb. For Rails < 7, use:
config.active_record.partial_writes = falseFor Rails 7+, use:
config.active_record.partial_inserts = falseAdding a non-unique index with more than three columns rarely improves performance.
class AddSomeIndexToUsers < ActiveRecord::Migration[7.1]
def change
add_index :users, [:a, :b, :c, :d]
end
endInstead, start an index with columns that narrow down the results the most.
class AddSomeIndexToUsers < ActiveRecord::Migration[7.1]
def change
add_index :users, [:b, :d]
end
endFor Postgres, be sure to add them concurrently.
To mark a step in the migration as safe, despite using a method that might otherwise be dangerous, wrap it in a safety_assured block.
class MySafeMigration < ActiveRecord::Migration[7.1]
def change
safety_assured { remove_column :users, :some_column }
end
endCertain methods like execute and change_table cannot be inspected and are prevented from running by default. Make sure what you’re doing is really safe and use this pattern.
Make operations safe by default.
- adding and removing an index
- adding a foreign key
- adding a check constraint
- setting NOT NULL on an existing column
Add to config/initializers/strong_migrations.rb:
StrongMigrations.safe_by_default = trueAdd your own custom checks with:
StrongMigrations.add_check do |method, args|
if method == :add_index && args[0].to_s == "users"
stop! "No more indexes on the users table"
end
endUse the stop! method to stop migrations.
Note: Since remove_column always requires a safety_assured block, it’s not possible to add a custom check for remove_column operations.
Postgres supports removing indexes concurrently, but removing them non-concurrently shouldn’t be an issue for most applications. You can enable this check with:
StrongMigrations.enable_check(:remove_index)Disable specific checks with:
StrongMigrations.disable_check(:add_index)Check the source code for the list of keys.
By default, checks are disabled when migrating down. Enable them with:
StrongMigrations.check_down = trueTo customize specific messages, create an initializer with:
StrongMigrations.error_messages[:add_column_default] = "Your custom instructions"Check the source code for the list of keys.
It’s extremely important to set a short lock timeout for migrations. This way, if a migration can’t acquire a lock in a timely manner, other statements won’t be stuck behind it. We also recommend setting a long statement timeout so migrations can run for a while.
Create config/initializers/strong_migrations.rb with:
StrongMigrations.lock_timeout = 10.seconds
StrongMigrations.statement_timeout = 1.hourOr set the timeouts directly on the database user that runs migrations. For Postgres, use:
ALTER ROLE myuser SET lock_timeout = '10s';
ALTER ROLE myuser SET statement_timeout = '1h';Note: If you use PgBouncer in transaction mode, you must set timeouts on the database user.
We recommend adding timeouts to config/database.yml to prevent connections from hanging and individual queries from taking up too many resources in controllers, jobs, the Rails console, and other places.
For Postgres:
production:
connect_timeout: 5
variables:
statement_timeout: 15s
lock_timeout: 10sNote: If you use PgBouncer in transaction mode, you must set the statement and lock timeouts on the database user as shown above.
For MySQL:
production:
connect_timeout: 5
read_timeout: 5
write_timeout: 5
variables:
max_execution_time: 15000 # ms
lock_wait_timeout: 10 # sec
For MariaDB:
production:
connect_timeout: 5
read_timeout: 5
write_timeout: 5
variables:
max_statement_time: 15 # sec
lock_wait_timeout: 10 # secFor HTTP connections, Redis, and other services, check out this guide.
There’s the option to automatically retry statements for migrations when the lock timeout is reached. Here’s how it works:
- If a lock timeout happens outside a transaction, the statement is retried
- If it happens inside the DDL transaction, the entire migration is retried (only applicable to Postgres)
Add to config/initializers/strong_migrations.rb:
StrongMigrations.lock_timeout_retries = 3Set the delay between retries with:
StrongMigrations.lock_timeout_retry_delay = 10.secondsTo mark migrations as safe that were created before installing this gem, create an initializer with:
StrongMigrations.start_after = 20230101000000Use the version from your latest migration.
If your development database version is different from production, you can specify the production version so the right checks run in development.
StrongMigrations.target_version = 10 # or "8.0.12", "10.3.2", etcThe major version works well for Postgres, while the full version is recommended for MySQL and MariaDB.
For safety, this option only affects development and test environments. In other environments, the actual server version is always used.
If your app has multiple databases with different versions, with Rails 6.1+, you can use:
StrongMigrations.target_version = {primary: 13, catalog: 15}Analyze tables automatically (to update planner statistics) after an index is added. Create an initializer with:
StrongMigrations.auto_analyze = trueOnly dump the schema when adding a new migration. If you use Git, add to config/environments/development.rb:
config.active_record.dump_schema_after_migration = `git status db/migrate/ --porcelain`.present?Columns can flip order in db/schema.rb when you have multiple developers. One way to prevent this is to alphabetize them. Add to config/initializers/strong_migrations.rb:
StrongMigrations.alphabetize_schema = trueWe recommend using a separate database user for migrations when possible so you don’t need to grant your app user permission to alter tables.
You probably don’t need this gem for smaller projects, as operations that are unsafe at scale can be perfectly safe on smaller, low-traffic tables.
- Rails Migrations with No Downtime
- PostgreSQL at Scale: Database Schema Changes Without Downtime
- An Overview of DDL Algorithms in MySQL
- MariaDB InnoDB Online DDL Overview
Thanks to Bob Remeika and David Waller for the original code and Sean Huber for the bad/good readme format.
Everyone is encouraged to help improve this project. Here are a few ways you can help:
- Report bugs
- Fix bugs and submit pull requests
- Write, clarify, or fix documentation
- Suggest or add new features
To get started with development:
git clone https://github.com/ankane/strong_migrations.git
cd strong_migrations
bundle install
# Postgres
createdb strong_migrations_test
bundle exec rake test
# MySQL and MariaDB
mysqladmin create strong_migrations_test
ADAPTER=mysql2 bundle exec rake test
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent