Migrations 29 and 35 consume hard drive
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.
Change History
(3)
| Owner: |
changed from ayleph to Jessica Tallon
|
| Status: |
new → in_progress
|
| Owner: |
Jessica Tallon removed
|
| Resolution: |
→ fixed
|
| Status: |
in_progress → closed
|
This should be fixed as of commit ccd9dab in master. Thanks for reporting it!