diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2021-07-30 03:10:03 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2021-07-30 03:10:03 +0300 |
| commit | 420215876fadcc44935e7937cb56f7ffe5212ecb (patch) | |
| tree | a24028043ba417bbdde620521e1940eb4ce727e1 /doc/development/iterating_tables_in_batches.md | |
| parent | e4df6a7c53ab6e9dd6d63516ca9e0ad143cfa17a (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, 2 insertions, 2 deletions
diff --git a/doc/development/iterating_tables_in_batches.md b/doc/development/iterating_tables_in_batches.md index 3f2b467fec9..fba6f2f616d 100644 --- a/doc/development/iterating_tables_in_batches.md +++ b/doc/development/iterating_tables_in_batches.md @@ -334,8 +334,8 @@ end The iteration uses the `id` column of the `projects` table. The batching does not affect the subquery. This means for each iteration, the subquery is executed by the database. This adds a constant "load" on the query which often ends up in statement timeouts. We have an unknown number -of confidential issues, the execution time and the accessed database rows depend on the data -distribution in the `issues` table. +of [confidential issues](../user/project/issues/confidential_issues.md), the execution time +and the accessed database rows depend on the data distribution in the `issues` table. NOTE: Using subqueries works only when the subquery returns a small number of rows. |