Postgres concurrency limit

Hi all I have a question due to dropping db connections? We are running one postgres server for our app but sometimes seeing messages that are related to postgres connection. I went to the logs an saw that we are hitting hard limit around 80. Is this normal?


I went to cli to check the config but max connections is at 300

NAME                            VALUE   UNIT    DESCRIPTION                                                                                     PENDING RESTART
wal-level                       replica         Sets the level of information written to the WAL. [minimal, replica, logical]                   false
max-wal-senders                 10              Sets the maximum number of simultaneously running WAL sender processes. (0, 262143)             false
max-connections                 300             Sets the maximum number of concurrent connections. (1, 262143)                                  false
maintenance-work-mem            65536   kB      Sets the maximum memory to be used for maintenance operations. (1024, 2147483647)               false
shared-buffers                  262144  8kB     Sets the number of shared memory buffers used by the server. (16, 1073741823)                   false
shared-preload-libraries        repmgr          Lists shared libraries to preload into server.                                                  false
max-replication-slots           10              Sets the maximum number of simultaneously defined replication slots. (0, 262143)                false
work-mem                        4096    kB      Sets the maximum memory to be used for query workspaces. (64, 2147483647)                       false
log-statement                   none            Sets the type of statements logged. [none, ddl, mod, all]                                       false
log-min-duration-statement      -1      ms      Sets the minimum execution time above which all statements will be logged. (-1, 2147483647)     false

Can this be resolved via cli?

Hi… Generally speaking, Single-Machine Legacy Postgres is suitable only for throwaway development servers—and wouldn’t have this many connections.

You mentioned in another thread that you were using Managed Postgres, elsewhere (?); that is really the only choice in production in my opinion (unless you’re an expert database administrator).

Hope this helps a little!

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.