Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kpBS4-00051S-9S for pgsql-admin@arkaria.postgresql.org; Tue, 15 Dec 2020 14:37:20 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kpBS3-0006vJ-3u for pgsql-admin@arkaria.postgresql.org; Tue, 15 Dec 2020 14:37:19 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kpBS2-0006vB-Sd for pgsql-admin@lists.postgresql.org; Tue, 15 Dec 2020 14:37:18 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kpBS0-0002g7-UO for pgsql-admin@postgresql.org; Tue, 15 Dec 2020 14:37:18 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 0BFEbEFU1167860; Tue, 15 Dec 2020 09:37:14 -0500 From: Tom Lane To: Atul Kumar cc: pgsql-admin Subject: Re: PostgreSQL: Number of waiting connections too high In-reply-to: References: Comments: In-reply-to Atul Kumar message dated "Tue, 15 Dec 2020 14:45:57 +0530" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1167858.1608043034.1@sss.pgh.pa.us> Date: Tue, 15 Dec 2020 09:37:14 -0500 Message-ID: <1167859.1608043034@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Atul Kumar writes: > I am getting below error of > PostgreSQL: Number of waiting connections too high. Hmm ... the other responses presumed that what you are running into is ERRCODE_TOO_MANY_CONNECTIONS (53300), but I'm not entirely convinced, because the standard wording of the message for that is "sorry, too many clients already". I think you have some client-side issue. Alternatively, maybe you are already using a connection pooler and this message is coming from that. In that case, you need to reconfigure the pooler to allow more clients. regards, tom lane