Query Performance Investigation - SELECT $1 AS one FROM "keys" WHERE "keys"."fingerprint"
<!--IssueSummary start-->
<details>
<summary>
Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards.
</summary>
- [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=334088)
</details>
<!--IssueSummary end-->
## Description
As the name implies, the purpose of the template is to detail underperforming queries for further investigation.
### SQL Statement
```sql
SELECT $1 AS one
FROM "keys"
WHERE "keys"."fingerprint" = $2
AND "keys"."id" != $3 LIMIT $4
```
`/application:web,correlation_id:01F7AQ70EKFJC69WM78Z70QJVE,endpoint_id:POST /api/:version/internal/allowed/`
### Requested Data points
Please provide as many of these fields as possible when submitting a query performance report.
- Queries per second 747\.6655367231638. This query comes up quite frequently during database peak performance issues. See search here: https://gitlab.com/search?group_id=1112072&project_id=1304532&repository_ref=&scope=notes&search=1014496000100469180&snippets=false
- QueryID - 1014496000100469180
- Database performance peak issue https://gitlab.com/gitlab-com/gl-infra/infrastructure/-/issues/13531
issue