| Table of Contents |
|---|
...
When using AWS Aurora, a nullable column can be added to existing large (100k rows+?) tables without causing downtime. However, the migration may still timeout in GoCD - so please coordinate the release with DevOps.
- Make a new field addition in model with null=True.
- Generate the model-change migrations locally.
- Create a pull request containing the model change and newly-generated migrations.
- Merge the migration pull request.
- The release process will run the migration and add the nullable column to table.
...
On AWS Aurora, indexes can be build on large tables without causing downtime, but this requires devops coordination as the migration may timeout in GoCD.
- Add the new index on model fields.
- Generate the model-change migrations locally.
- Make pull request containing the model change and newly-generated migrations.
- Merge the migration pull request.
- Release will run the migration and add the index to table.
...
- Is there a primary key? How fast will the table grow? Should the primary key be a bigint (more than 4b rows)? In general, use the Django default generated auto incrementing id for a primary key.
- Is there a process for identifying and trimming expired rows? Is there an appropriate index that will prevent a full table scan during cleanup?
- What are the most common queries? Are there indexes to support them?
- Should there be unique constraints?
...