| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | MichaelDBA <MichaelDBA(at)sqlexec(dot)com> |
| Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, "Heckler, Kim M" <kim(dot)heckler(at)nationwide(dot)com>, "pgsql-admin(at)lists(dot)postgresql(dot)org" <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Database log in |
| Date: | 2024-01-25 00:22:13 |
| Message-ID: | 237334.1706142133@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
MichaelDBA <MichaelDBA(at)sqlexec(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heckler, Kim M | 2024-01-25 14:25:02 | Re: Database log in |
| Previous Message | MichaelDBA | 2024-01-24 22:24:46 | Re: Database log in |