Django迁移难题：回滚代码后PostgreSQL环境适配问题求助

Hey there, let’s break down your problem and walk through solutions that should get you back on track.

Should you switch to SQLite for development? #

Short answer: It’s a temporary band-aid, not a long-term fix.

• Using SQLite in dev can simplify environment consistency headaches right now, especially if your migration woes are blocking progress. It’s lightweight and doesn’t require a separate server, so you can quickly test your rolled-back code’s logic.
• But don’t make it permanent if your production environment uses PostgreSQL. SQLite lacks support for many PostgreSQL-specific features (like JSONB fields, full-text search, or certain constraint types), so you’ll likely hit compatibility issues when you eventually deploy to production. Stick with PostgreSQL for dev if you can resolve the migration problem—it’ll save you pain later.

Fixing the PostgreSQL Migration Rollback Mess #

Most of these issues happen because your code, migration files, and database state are out of sync. Here’s a step-by-step cleanup process that usually works:

1. Wipe all migration traces completely

   • Delete all files in every app’s migrations/ folder except __init__.py (don’t remove this file—it tells Django the folder is a Python package).
   • Delete all __pycache__ folders across your project (both at the root and inside each app).
   • Log into your PostgreSQL server, drop the existing database, and create a brand-new empty one. Use these commands (replace db_name with your database name):

     DROP DATABASE db_name;
     CREATE DATABASE db_name;
     

2. Rebuild migrations from scratch for your rolled-back code

   • Don’t use syncdb—it’s deprecated in Django 1.9+ and skips migration tracking, which will only make inconsistencies worse. Stick with Django’s official migration workflow.
   • Generate fresh migrations for each app individually (this avoids cross-app dependency issues):

     python manage.py makemigrations app_name
     

   • Run the migrations to populate your new database:

     python manage.py migrate
     

3. Sync migration files when rolling back code

   • The biggest mistake people make is only rolling back their app code, not the corresponding migration files. If you’re using Git, after rolling back your code to an older commit, run this to sync your migration files too:

     git checkout <your-rollback-commit-hash> -- */migrations/
     

   • This ensures your migration files match the schema expected by your rolled-back code.

4. Check PostgreSQL version compatibility
   Django 2.0.5 was released in 2018, and while it supports PostgreSQL 9.4+, newer PostgreSQL versions (12+) might have subtle changes that break compatibility with older Django versions. Try downgrading PostgreSQL to a version that was stable when Django 2.0.5 came out (like PostgreSQL 11.x) to see if that fixes the "old code can’t recognize PostgreSQL environment" error.

Have other developers faced this? #

Absolutely! This is a common pain point for teams working with Django migrations, especially when rolling back code without syncing migration state. Many developers have posted about similar issues on community forums—almost always the root cause is a mismatch between code, migration files, and the actual database schema. The fix almost always boils down to aligning those three pieces properly.

内容的提问来源于stack exchange，提问作者Kenneth Hutchison