We had the folllowing problem: - We created a migration file that was adding a new field in one table - In the same migration file of the schema migration, we also added a data migration to populate this field
Locally and in our sandbox the migration worked fine, without problem. It took ~30 seconds. But in production, the migration stuck for more than 20 minutes and we have to kill it. The only difference between our sandbox and production system is that in the production we have postres replication. To test more the problem, I added a postgres replica in sandbox and it also stuck in that migration. So the problem is: When we have: - A schema migration and a data migration in the same migration file - And a postgres replica active The migration stuck. If I separate the data migration in another file, the migration works fine. If I add "atomic = False" in the migration declaration, everything works, even using just one file for schema and data migration. I looking to know if it's a bug or some detail in our configuration. Someone knows anything about it? More ideas about how to debug it? Thanks. -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/bcc98321-deb2-4b70-928b-014d89814097%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
