diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2023-04-04 06:10:42 +0000 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2023-04-04 06:10:42 +0000 |
| commit | f3f3149fc5249ad27378e4f2c22b8c3ff429a493 (patch) | |
| tree | f50aec11527fd4f336bc0cf03387be828c66cd3c /doc/development/database | |
| parent | 0555f8b0429486b14e36f92152587030db33708c (diff) | |
| download | gitlab-ce-f3f3149fc5249ad27378e4f2c22b8c3ff429a493.tar.gz | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development/database')
| -rw-r--r-- | doc/development/database/adding_database_indexes.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/development/database/adding_database_indexes.md b/doc/development/database/adding_database_indexes.md index 1e3a1de9b69..0bb175598a6 100644 --- a/doc/development/database/adding_database_indexes.md +++ b/doc/development/database/adding_database_indexes.md @@ -448,7 +448,7 @@ You must test the database index changes locally before creating a merge request the post-deploy migration has been executed in the production database. For more information, see [How to determine if a post-deploy migration has been executed on GitLab.com](https://gitlab.com/gitlab-org/release/docs/-/blob/master/general/post_deploy_migration/readme.md#how-to-determine-if-a-post-deploy-migration-has-been-executed-on-gitlabcom). 1. In the case of an [index removed asynchronously](#schedule-the-index-to-be-removed), wait - until the next week so that the index can be created over a weekend. + until the next week so that the index can be removed over a weekend. 1. Use Database Lab [to check if removal was successful](database_lab.md#checking-indexes). [Database Lab](database_lab.md) should report an error when trying to find the removed index. If not, the index may still exist. |