<!--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=29603) </details> <!--IssueSummary end--> We recently dealt with an issue where a user's external Postgres database configuration causing the same pipelines to be triggered multiple times. In this particular case, they have `default_transaction_isolation` configured as `repeatable read` instead of `read committed` (internal only ZD ref: https://gitlab.zendesk.com/agent/tickets/119156) I've documented the troubleshooting error in our documentation here: https://gitlab.com/gitlab-org/omnibus-gitlab/merge_requests/3359/diffs It would be great if our `gitlab:check` can catch these kinds of potential database configuration issues.