From: Tom Lane <tgl@sss.pgh.pa.us>
To: adolfo flores <adolfoflores2211@gmail.com>
cc: pgsql-general@lists.postgresql.org
Subject: Re: Getting error "too many clients already" despite having a db connection limit set
In-reply-to: <CADM4kyuO39mr8E_xDw4GGi2v9gCK0dq52fKj40FcsXJeKxgRrA@mail.gmail.com>
References: <CADM4kyuO39mr8E_xDw4GGi2v9gCK0dq52fKj40FcsXJeKxgRrA@mail.gmail.com>
Comments: In-reply-to adolfo flores <adolfoflores2211@gmail.com>
	message dated "Mon, 16 Jun 2025 10:29:28 -0600"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <536521.1750091949.1@sss.pgh.pa.us>
Date: Mon, 16 Jun 2025 12:39:09 -0400
Message-ID: <536522.1750091949@sss.pgh.pa.us>
Archived-At: <https://www.postgresql.org/message-id/536522.1750091949%40sss.pgh.pa.us>
Precedence: bulk

adolfo flores <adolfoflores2211@gmail.com> writes:
> I hope you can help me with an issue we're experiencing. We have an app
> running on Kubernetes that opens a huge number of connections within a
> couple of seconds.

You need to fix that app to be less unfriendly, or maybe put it behind
a connection pooler.

> Is it expected behavior to reach the max_connections limit when that app
> opens many connections in a short period of time, even if a connection
> limit is set for that database and everything else uses no more than 10% of
> the max_connections?

It takes a finite amount of time for a new backend process to figure
out which database it's supposed to connect to and then detect whether
the per-DB connection limit is exceeded.  In the meantime, that
session does count against the global limit, so yeah this isn't
surprising if the connection arrival rate is high enough.

			regards, tom lane