Yandex Cloud
Search
Contact UsGet started
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • AI for business
    • Business tools
  • 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
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
© 2025 Direct Cursus Technology L.L.C.
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
  1. Managed PostgreSQL
  2. All solutions for Managed PostgreSQL

All solutions for Managed Service for PostgreSQL

Written by
Yandex Cloud
Updated at November 27, 2023

Sample configurations and use cases for Managed Service for PostgreSQL

  • Understanding the Conn limit parameter
  • How to set up SQL query filtering
  • How to enable SQL query logging

Solutions for known Managed Service for PostgreSQL issues

  • Resolving the consequences of cluster storage overflow with WAL logs
  • Managed Service for PostgreSQL cluster switches to the Unknown state immediately after creation
  • 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
  • Resolving the psql error: "error: could not translate host name to address: nodename nor servname provided, or not known"
  • Resolving the error: Unrecognized configuration parameter "stats_temp_directory"
  • Restoring health of 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
  • Resolving issues with updating configurations of clusters with local-ssd disks

Was the article helpful?

Previous
Error saving an SQL dump of a database from a Managed Service for MySQL cluster using mysqldump
Next
Recovering a Managed Services for PostgreSQL cluster after its disks become Read Only
© 2025 Direct Cursus Technology L.L.C.