Yandex Cloud
Search
Contact UsGet started
  • Blog
  • Pricing
  • Documentation
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • ML & AI
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Customer Stories
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
  • Blog
  • Pricing
  • Documentation
Yandex project
© 2025 Yandex.Cloud LLC
All solutions
    • All solutions for Managed PostgreSQL
    • Recovering a Managed Services for PostgreSQL cluster after its disks become Read Only
    • You are unable to delete your Managed Service for PostgreSQL cluster in the Dead status if deletion protection was enabled for it
    • Managed Service for PostgreSQL cluster switches to the Unknown state immediately after creation
    • Resolving issues with updating configurations of clusters with local-ssd disks
    • Resolving the consequences 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"
    • Resolving the error Unrecognized configuration parameter "stats_temp_directory"
    • Resolving the "max_connections conn_limit is too high" error
    • Resolving the "422 UNPROCESSABLE ENTITY The specified extension <'ext_name'> is not present in shared_preload_libraries" error
    • Understanding the Conn limit parameter
    • How to set up SQL query filtering
    • How to enable SQL query logging

In this article:

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

Resolving the "max_connections conn_limit is too high" error

Written by
Yandex Cloud
Updated at November 27, 2023
  • Issue description
  • Solution

Issue descriptionIssue description

You see the max_connections conn_limit is too high error.

SolutionSolution

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

Note

Yandex Managed Service for PostgreSQL reserves 15 connections for service users on each PostgreSQL host.

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

Was the article helpful?

Previous
Resolving the error Unrecognized configuration parameter "stats_temp_directory"
Next
Resolving the "422 UNPROCESSABLE ENTITY The specified extension <'ext_name'> is not present in shared_preload_libraries" error
Yandex project
© 2025 Yandex.Cloud LLC