From: Tom Lane <tgl@sss.pgh.pa.us>
To: MichaelDBA <MichaelDBA@sqlexec.com>
Cc: David G. Johnston <david.g.johnston@gmail.com>
Cc: Heckler, Kim M <kim.heckler@nationwide.com>
Cc: pgsql-admin@lists.postgresql.org <pgsql-admin@lists.postgresql.org>
Subject: Re: Database log in
Date: Wed, 24 Jan 2024 19:22:13 -0500
Message-ID: <237334.1706142133@sss.pgh.pa.us> (raw)
In-Reply-To: <c3c3ed0c-cf0f-3030-8610-00b055c17d41@sqlexec.com>
References: <SA1PR07MB8484F96961B8B73832FB3F4B867B2@SA1PR07MB8484.namprd07.prod.outlook.com>
<CAKFQuwZGywd1hUbvgq+4j9eCEZWtDYL7c4WFofy01ygOXtjYiw@mail.gmail.com>
<c3c3ed0c-cf0f-3030-8610-00b055c17d41@sqlexec.com>
MichaelDBA <MichaelDBA@sqlexec.com> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, MichaelDBA@sqlexec.com, david.g.johnston@gmail.com, kim.heckler@nationwide.com, pgsql-admin@lists.postgresql.org
Subject: Re: Database log in
In-Reply-To: <237334.1706142133@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox