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:

  • Issue description
  • Solution
  1. Managed Service for PostgreSQL
  2. Resolving the `max_connections conn_limit is too high` error

Fixing the max_connections conn_limit is too high error

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

Issue descriptionIssue description

You get the max_connections conn_limit is too high error when connecting to Managed Service for PostgreSQL.

SolutionSolution

By default, Managed Service for PostgreSQL limits the maximum number of connections to each PostgreSQL cluster host. This maximum value is calculated as follows: 200 × <number of vCPUs on each host>. For an s1.micro class cluster, the default max_connections value is 400, and it cannot be increased. To have more connections, you need to upgrade the cluster class.

Note

Managed Service for PostgreSQL reserves 15 connections for service users per PostgreSQL host.

For example, if max_connections is set to 100 for the cluster, you can reserve no more than 85 connections for your cluster users.

Was the article helpful?

Previous
Resolving the `Unrecognized configuration parameter stats_temp_directory` error
Next
Resolving the `Must be superuser to create this extension` error
© 2025 Direct Cursus Technology L.L.C.