Migrations 29 and 35 consume hard drive
|Reported by:||ayleph||Owned by:|
Per the devel list conversion, database migrations 29 and 35 consume a very large amount of hard drive space on instances with numerous database entries. A proposed solution would be to run db.commit after every entry instead of once at the end. This may make the entire migration slower, but it will hopefully prevent consuming all storage space.