Merge pull request #209157 from AwdotiaRomanowna/patch-1

[PostgreSQL] inaccurate data

Author: prmerger-automator[bot]

articles/postgresql/single-server/concepts-limits.md

@@ -42,7 +42,7 @@ When connections exceed the limit, you may receive the following error:
 > [!IMPORTANT]
 > For best experience, we recommend that you use a connection pooler like pgBouncer to efficiently manage connections.
 
-A PostgreSQL connection, even idle, can occupy about 10MB of memory. Also, creating new connections takes time. Most applications request many short-lived connections, which compounds this situation. The result is fewer resources available for your actual workload leading to decreased performance. A connection pooler that decreases idle connections and reuses existing connections will help avoid this. To learn more, visit our [blog post](https://techcommunity.microsoft.com/t5/azure-database-for-postgresql/not-all-postgres-connection-pooling-is-equal/ba-p/825717).
+A PostgreSQL connection, even idle, can occupy up to 2MB of memory. Also, creating new connections takes time. Most applications request many short-lived connections, which compounds this situation. The result is fewer resources available for your actual workload leading to decreased performance. A connection pooler that decreases idle connections and reuses existing connections will help avoid this. To learn more, visit our [blog post](https://techcommunity.microsoft.com/t5/azure-database-for-postgresql/not-all-postgres-connection-pooling-is-equal/ba-p/825717).
 
 ## Functional limitations