diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2023-04-20 00:12:57 +0000 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2023-04-20 00:12:57 +0000 |
| commit | 8277a5b4ba05fe11174397c689c66cef5c06fc38 (patch) | |
| tree | c4abbec1509476efbb14c040045ca163042de3bf /doc/development/database_review.md | |
| parent | f46a8dbf1a0999e27dfeddd258096ef97def8d64 (diff) | |
| download | gitlab-ce-8277a5b4ba05fe11174397c689c66cef5c06fc38.tar.gz | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development/database_review.md')
| -rw-r--r-- | doc/development/database_review.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/development/database_review.md b/doc/development/database_review.md index 1f653f8af94..feac0b3098d 100644 --- a/doc/development/database_review.md +++ b/doc/development/database_review.md @@ -125,7 +125,7 @@ the following preparations into account. test its execution using `CREATE INDEX CONCURRENTLY` in [Database Lab](database/database_lab.md) and add the execution time to the MR description: - Execution time largely varies between Database Lab and GitLab.com, but an elevated execution time from Database Lab can give a hint that the execution on GitLab.com is also considerably high. - - If the execution from Database Lab is longer than `1h`, the index should be moved to a [post-migration](database/post_deployment_migrations.md). + - If the execution from Database Lab is longer than `10 minutes`, the [index](database/adding_database_indexes.md) should be moved to a [post-migration](database/post_deployment_migrations.md). Keep in mind that in this case you may need to split the migration and the application changes in separate releases to ensure the index is in place when the code that needs it is deployed. - Manually trigger the [database testing](database/database_migration_pipeline.md) job (`db:gitlabcom-database-testing`) in the `test` stage. |