📚 Sync docs from alaudadevops/gitlab-ce-operator on e4a3942c9126686ba610a4c8a9a053cd902d12ca

Source: feat: upgrade gitlab to  18.2.8
Author: mingfu
Ref: refs/heads/release-18.2
Commit: e4a3942c9126686ba610a4c8a9a053cd902d12ca

This commit automatically syncs documentation changes from the source-docs repository.

🔗 View source commit: AlaudaDevops/gitlab-ce-operator@e4a3942
🤖 Synced on 2025-10-13 06:01:09 UTC

Author: nanjingfm

.github/SYNC_INFO.md

@@ -1,10 +1,10 @@
 # Documentation Sync Information
 
-- **Last synced**: 2025-10-13 03:07:54 UTC
+- **Last synced**: 2025-10-13 06:01:09 UTC
 - **Source repository**: alaudadevops/gitlab-ce-operator
-- **Source commit**: [2ec027ea77694df9791c3588886597891586fb39](https://github.com/alaudadevops/gitlab-ce-operator/commit/2ec027ea77694df9791c3588886597891586fb39)
+- **Source commit**: [e4a3942c9126686ba610a4c8a9a053cd902d12ca](https://github.com/alaudadevops/gitlab-ce-operator/commit/e4a3942c9126686ba610a4c8a9a053cd902d12ca)
 - **Triggered by**: nanjingfm
-- **Workflow run**: [#38](https://github.com/alaudadevops/gitlab-ce-operator/actions/runs/18453925602)
+- **Workflow run**: [#39](https://github.com/alaudadevops/gitlab-ce-operator/actions/runs/18456578987)
 
 ## Files synced:
 - docs/

docs/en/trouble_shooting/01_pg_connection_limit_error.mdx

@@ -0,0 +1,39 @@
+# PostgreSQL Connection Limit Error
+
+## Problem Description
+
+Gitlab component logs (for example sidekiq, webservice, praefect) show database errors such as: `pq: sorry, too many clients already`
+
+## Root Cause
+
+Gitlab opened more concurrent PostgreSQL connections than the database allows (exceeded PostgreSQL `max_connections`).
+
+## Troubleshooting
+
+Check the logs of the Gitlab Deployments. Confirm if the `pq: sorry, too many clients already` error message is present.
+
+```bash
+kubectl -n <NAMESPACE> logs <RELEASE>-praefect-xxxxx
+kubectl -n <NAMESPACE> logs <RELEASE>-sidekiq-all-in-1-v2-xxxxx
+kubectl -n <NAMESPACE> logs <RELEASE>-webservice-default-xxxxx
+```
+
+## Solution
+
+If PostgreSQL's `max_connections` is too low for your Gitlab scale, increase it on your PostgreSQL side. The exact steps depend on how you manage PG and are out of scope here.
+
+You can use the following command to check PostgreSQL capacity and current usage:
+
+```sql
+-- Show the global upper limit on concurrent connections allowed by this PostgreSQL instance.
+-- Note: the effective limit available to non-superusers ≈ max_connections - superuser_reserved_connections.
+SHOW max_connections;
+
+-- Show how many connections are reserved for superusers,
+-- so administrators can still log in when all regular slots are taken.
+SHOW superuser_reserved_connections;
+
+-- Count the total number of currently open backend connections across all databases and states
+-- (e.g., active, idle, idle in transaction, autovacuum, replication).
+SELECT count(*) AS current_connections FROM pg_stat_activity;
+```