Group-level vulnerability report page query is using too many shared buffers for some filters
Summary
The group-level SQL query generated for the GraphQL API is using too many shared buffers for some filtering options.
Steps to reproduce
Check the following execution plan: https://console.postgres.ai/gitlab/gitlab-production-main/sessions/30682/commands/95255
What is the current bug behavior?
The fired SQL query is using too many shared buffers which is causing statement timeout.
What is the expected correct behavior?
The query shouldn't use that many shared buffers.
Output of checks
This bug happens on GitLab.com
Possible fixes
Filter out impossible-to-match severity values when before
or after
cursors are provided.
Edited by Mehmet Emin INAC