BigW Consortium Gitlab
In this particular case the use of UNION ALL leads to a better query plan compared to using 1 big query that uses an OR statement to combine different data sources. See https://gitlab.com/gitlab-org/gitlab-ce/issues/38508 for more information.
Name |
Last commit
|
Last update |
---|---|---|
.. | ||
api/helpers | Loading commit data... | |
banzai | Loading commit data... | |
bitbucket | Loading commit data... | |
constraints | Loading commit data... | |
container_registry | Loading commit data... | |
github | Loading commit data... | |
gitlab | Loading commit data... | |
json_web_token | Loading commit data... | |
mattermost | Loading commit data... | |
microsoft_teams | Loading commit data... | |
rspec_flaky | Loading commit data... | |
system_check | Loading commit data... | |
additional_email_headers_interceptor_spec.rb | Loading commit data... | |
after_commit_queue_spec.rb | Loading commit data... | |
disable_email_interceptor_spec.rb | Loading commit data... | |
event_filter_spec.rb | Loading commit data... | |
expand_variables_spec.rb | Loading commit data... | |
extracts_path_spec.rb | Loading commit data... | |
feature_spec.rb | Loading commit data... | |
file_size_validator_spec.rb | Loading commit data... | |
gitlab_spec.rb | Loading commit data... | |
repository_cache_spec.rb | Loading commit data... | |
system_check_spec.rb | Loading commit data... |