`delete_all` doesn't support limit, so you'd need to subquery
that. And instead of subquerying with `where(id: query)`, it's better
to use an `INNER JOIN`. This method also works with MySQL, while
subquerying doesn't (without another layer of subquerying)

Reference:
https://stackoverflow.com/questions/17892762/mysql-this-version-of-mysql-doesnt-yet-support-limit-in-all-any-some-subqu/17892886#17892886

The 9.4 to 9.5 and 9.5 to 10.0 guides missed a closing backtick. This
was corrected in the 10.0 to 10.1 guide, from which subsequent guides
were written without the error.

Due to a missing `s`, a link to the blog archive
for releases was broken.

This adds a development guide explaining that we are going to use
feature flags more often, why, what the benefits are, and so on.

See https://gitlab.com/gitlab-org/gitlab-ce/issues/49619 for more
information.

This enhances a few performance guideline titles in the development
README, making it easier to understand what topics they cover.

Rémy Coutable authored 6 years ago and Daniel Davison committed 6 years ago

Signed-off-by: Rémy Coutable <remy@rymai.me>
Signed-off-by: ddavison <ddavison@gitlab.com>

I think that's all the k8s resources created AFAIK

Add a Helm Chart column for each application so that users can cross-reference RBAC resouce documentation

Document `gitlab` service account creation. Re-word to make documentation flow in both cluster addtion and creation scenarios

Add table of resources created for ease of scannning

This is based on the discussion in
https://gitlab.com/gitlab-org/gitlab-ce/issues/49653 and the example
merge request found at
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/20908. The idea
is fairly straightforward: we define a variety of abstractions, then
state which can reuse which. This should ultimately foster _better_ code
reuse, make it easier to debug problems, and make it harder to
accidentally introduce a performance regression.