From 84dcde45853fb4851d528d6d37860fda4b336b6b Mon Sep 17 00:00:00 2001
From: Christian Lenz <55680468+lenzch@users.noreply.github.com>
Date: Thu, 2 Jul 2026 09:45:13 +0200
Subject: [PATCH] Remove duplicate connection limit details

Removed duplicate information about PostgreSQL connection limits.
---
 learn-performance.md | 2 --
 1 file changed, 2 deletions(-)

diff --git a/learn-performance.md b/learn-performance.md
index 8913abc..bb4f766 100644
--- a/learn-performance.md
+++ b/learn-performance.md
@@ -44,8 +44,6 @@ Allocating larger amounts of memory (outside of the shared buffer pool) to your
 
 {{site.data.keyword.databases-for-postgresql}} sets the maximum number of connections to your PostgreSQL database to **115**. 15 connections are reserved for the superuser to maintain the state and integrity of your database, and 100 connections are available for you and your applications. After the connection limit is reached, any attempts at starting a new connection results in an error. To prevent overwhelming your deployment with connections, use connection pooling, or scale your deployment and increase its connection limit. For more information, see the [Managing PostgreSQL connections](/docs/databases-for-postgresql?topic=databases-for-postgresql-managing-connections) page.
 
-{{site.data.keyword.databases-for-postgresql}} sets the maximum number of connections to your PostgreSQL database to **115**. 15 connections are reserved for the superuser to maintain the state and integrity of your database, and 100 connections are available for you and your applications. After the connection limit is reached, any attempts at starting a new connection results in an error. To prevent overwhelming your deployment with connections, use connection pooling, or scale your deployment and increase its connection limit. For more information, see [Managing PostgreSQL connections](/docs/databases-for-postgresql?topic=databases-for-postgresql-managing-connections).
-
 ## Performance troubleshooting
 {: #performance_troubleshooting}