| From: | "Heckler, Kim M" <kim(dot)heckler(at)nationwide(dot)com> |
|---|---|
| To: | "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 14:25:02 |
| Message-ID: | SA1PR07MB8484CBE9384C96B04674EAA3867A2@SA1PR07MB8484.namprd07.prod.outlook.com |
| Views: | Raw Message | Whole Thread | 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
>>
Auth method is local password. The AWS RDS Instance does have Kerberos enable so there is ONE role
that authenticates via AD. I was thinking, maybe, that the local ID was mistakenly trying to authenticate
via AD, failing, and then authenticating locally?? I do have a ticket open with AWS to inquire about this.
Also, I will use strace to gather more info.
Thank you, Kim.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | lejeczek | 2024-01-26 14:17:40 | max_wal_senders - stuck on |
| Previous Message | Tom Lane | 2024-01-25 00:22:13 | Re: Database log in |