diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2020-12-11 09:10:17 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2020-12-11 09:10:17 +0300 |
| commit | 12d3a6f92190feeec2c36262a0344da00f228dcd (patch) | |
| tree | dc59acdbf46572001e733dfa7771eeed930fb871 /doc/development/iterating_tables_in_batches.md | |
| parent | 07116000f2e4995de8be756fd43c1e7e63507f90 (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development/iterating_tables_in_batches.md')
| -rw-r--r-- | doc/development/iterating_tables_in_batches.md | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/doc/development/iterating_tables_in_batches.md b/doc/development/iterating_tables_in_batches.md index 45f76bfa2b0..3953e7097dd 100644 --- a/doc/development/iterating_tables_in_batches.md +++ b/doc/development/iterating_tables_in_batches.md @@ -61,7 +61,9 @@ In case the column is not unique (no unique index definition), calling the `dist When dealing with data migrations the preferred way to iterate over large volume of data is using `EachBatch`. -A special case of data migration is a background migration where the actual data modification is executed in a background job. The migration code that determines the data ranges (slices) and schedules the background jobs uses `each_batch`. More info: [background migration scheduling](background_migrations.md#scheduling) +A special case of data migration is a [background migration](background_migrations.md#scheduling) +where the actual data modification is executed in a background job. The migration code that determines +the data ranges (slices) and schedules the background jobs uses `each_batch`. ## Efficient usage of `each_batch` |