Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rSnVc-00FzH9-Oq for pgsql-admin@arkaria.postgresql.org; Thu, 25 Jan 2024 00:22:21 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1rSnVb-009yxA-Mk for pgsql-admin@arkaria.postgresql.org; Thu, 25 Jan 2024 00:22:19 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rSnVb-009yx2-Bj for pgsql-admin@lists.postgresql.org; Thu, 25 Jan 2024 00:22:19 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rSnVY-003YdH-Fm for pgsql-admin@lists.postgresql.org; Thu, 25 Jan 2024 00:22: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 40P0MDP7237335; Wed, 24 Jan 2024 19:22:13 -0500 From: Tom Lane To: MichaelDBA cc: "David G. Johnston" , "Heckler, Kim M" , "pgsql-admin@lists.postgresql.org" Subject: Re: Database log in In-reply-to: References: Comments: In-reply-to MichaelDBA message dated "Wed, 24 Jan 2024 17:24:46 -0500" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <237333.1706142133.1@sss.pgh.pa.us> Content-Transfer-Encoding: 8bit Date: Wed, 24 Jan 2024 19:22:13 -0500 Message-ID: <237334.1706142133@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk MichaelDBA writes: > I don't have a problem with hundreds or thousands of logins per minute > on RDS or bare metal, even with only 8 CPUs and 32GB RAM.  There is > something else in play here... Yeah. The OP didn't mention the authentication method in use, but I could believe some sort of performance glitch if it consults an external server (for Kerberos, AD, LDAP, etc). Or maybe it's basically a network problem between client and server. regards, tom lane