Re: [PATCH] Exponential backoff for auth_delay - Mailing list pgsql-hackers

From Jacob Champion
Subject Re: [PATCH] Exponential backoff for auth_delay
Date
Msg-id CAOYmi+k2jkTPeWxCvSi7qzAGLsckQyAyiuZcNjosNJpOBjjo2g@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] Exponential backoff for auth_delay  (Michael Banck <mbanck@gmx.net>)
Responses Re: [PATCH] Exponential backoff for auth_delay
List pgsql-hackers
On Wed, Mar 6, 2024 at 2:45 PM Michael Banck <mbanck@gmx.net> wrote:
> In order to at least make case 2 not worse for exponential backoff, we
> could maybe disable it (and just wait for auth_delay.milliseconds) once
> MAX_CONN_RECORDS is full. In addition, maybe MAX_CONN_RECORDS should be
> some fraction of max_connections, like 25%?

(Our mails crossed; hopefully I've addressed the other points.)

I think solutions for case 1 and case 2 are necessarily at odds under
the current design, if auth_delay relies on slot exhaustion to do its
work effectively. Weakening that on purpose doesn't make much sense to
me; if a DBA is uncomfortable with the DoS implications then I'd argue
they need a different solution. (Which we could theoretically
implement, but it's not my intention to sign you up for that. :D )

--Jacob



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Injection points: some tools to wait and wake
Next
From: Alexander Korotkov
Date:
Subject: Re: Stack overflow issue