The failed migration’s transaction rolled back, so the database is at
the prior version. Look at the underlying exception
(permission denied, column already exists, etc.) and
fix the underlying cause. Once the fix is in place, redeploy — the
auto-migrator will retry the same migration from the same point.
The most common cause for first-time installs is missing privileges.
Run sql/migrator_prep.sql as the postgres superuser
(see Upgrading an existing install).