max_connections parameter: too_many_connections error

From: Shital A <brightuser2019(at)gmail(dot)com>
To: pgsql-general(at)lists(dot)postgresql(dot)org, pgsql-admin(at)lists(dot)postgresql(dot)org
Subject: max_connections parameter: too_many_connections error
Date: 2019-09-17 12:43:06
Message-ID: CAMp7vw-DdZUXA16ee_HpFdEj3Rw5+AvUHdXHTxfbOddheFNo=A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-general

*Hello*,

We are working on a payments systems which uses postgreSql 9.6 as backend
DB and blockchain technology. The database is setup in HA in master-standby
mode using pacemaker on Linux 7.6.

*We are new to postgres and ne*ed help in deciding how to set value for
max_connections on DB.

1. How can we decide on optimal value for max_connections for a given
setup/server? I checked many posts saying that even 1000 is considered as a
very high value but we are hitting the error too_many_connections due to
Max_connections value limit.

2. We usee hikari pool on the client side but that even has limitations.
Implementing pg_bouncer is another suggestion in the posts. In a HA setup,
do we have to set it up on both primary standby?

Please provide your advice/suggestions.

Thanks.

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Scot Kreienkamp 2019-09-17 13:24:00 RE: max_connections parameter: too_many_connections error
Previous Message Ashkar Dev 2019-09-17 11:56:30 Re: PostgreSQL License

Browse pgsql-general by date

  From Date Subject
Next Message Scot Kreienkamp 2019-09-17 13:24:00 RE: max_connections parameter: too_many_connections error
Previous Message Ashkar Dev 2019-09-17 11:56:30 Re: PostgreSQL License