Yandex Cloud
Search
Contact UsTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
  • Marketplace
    • Featured
    • Infrastructure & Network
    • Data Platform
    • AI for business
    • Security
    • DevOps tools
    • Serverless
    • Monitoring & Resources
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
    • Price calculator
    • Pricing plans
  • Customer Stories
  • Documentation
  • Blog
© 2025 Direct Cursus Technology L.L.C.
All solutions
    • All solutions for Managed Service for PostgreSQL
    • Restoring a Managed Service for PostgreSQL cluster after running out of free storage space
    • You are unable to delete your Managed Service for PostgreSQL cluster in the `DEAD` status if it has deletion protection enabled
    • Managed Service for PostgreSQL cluster switches to `UNKNOWN` once created
    • Resolving issues with updating configurations of clusters with `local-ssd` disks
    • Resolving the issue of cluster storage overflow with WAL logs
    • Resolving the `psql error could not translate host name to address nodename nor servname provided, or not known` error
    • Resolving the `Unrecognized configuration parameter stats_temp_directory` error
    • Resolving the `max_connections conn_limit is too high` error
    • Resolving the `Must be superuser to create this extension` error
    • Fixing the `terminating connection due to administrator command` and `ERROR: odyssey: remote server read/write error` errors
    • Resolving the `422 UNPROCESSABLE ENTITY The specified extension <'ext_name'> is not present in shared_preload_libraries` error
    • How `Conn limit` works
    • How to set up SQL query filtering
    • How to enable SQL query logging

In this article:

  • Case description
  • Solution
  1. Managed Service for PostgreSQL
  2. How `Conn limit` works

How Conn limit works

Written by
Yandex Cloud
Updated at December 17, 2025
  • Case description
  • Solution

Case descriptionCase description

You need to understand how the Conn limit parameter works in Managed Service for PostgreSQL.

SolutionSolution

Conn limit sets the maximum allowed number of connections per user. In session pooling, this setting limits the number of user connections to each host in a PostgreSQL cluster.

Here are the basic principles of session pooling:

  1. When creating a user, Managed Service for PostgreSQL reserves for this user 50 connections to each host in a PostgreSQL cluster by default. The minimum number of connections per user is 1.
  2. The total number of connections reserved for users must not exceed the Max connections value. Managed Service for PostgreSQL reserves 15 service connections per host.

For example, if the cluster is set to "max_connections": 100, you can reserve a maximum of 85 connections per cluster host for users. At the same time, the sum of the Conn limit values for all users in the cluster must not exceed 85.

Note

Max connections sets the maximum number of concurrent connections to a PostgreSQL host. The minimum value is 1. The maximum and default values are host class-dependent and calculated as follows:

200 × <Number of vCPUs per host>

Hosts with a guaranteed vCPU share below 100% (burstable) use fixed maximum values:

  • b1.nano, b1.micro, b2.nano, b2.micro: 100
  • b1.medium, b2.medium: 200

By default, the maximum value is used.

You can find detailed information in this article.

Was the article helpful?

Previous
Resolving the `422 UNPROCESSABLE ENTITY The specified extension <'ext_name'> is not present in shared_preload_libraries` error
Next
How to set up SQL query filtering
© 2025 Direct Cursus Technology L.L.C.