Re: [PATCH] Exponential backoff for auth_delay
От | Jacob Champion |
---|---|
Тема | Re: [PATCH] Exponential backoff for auth_delay |
Дата | |
Msg-id | CAOYmi+nkZ+BbmsbdXZEaULrv+fqL9gx1uyEBOKKNS8zYCy65dA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [PATCH] Exponential backoff for auth_delay (Jacob Champion <jacob.champion@enterprisedb.com>) |
Ответы |
Re: [PATCH] Exponential backoff for auth_delay
|
Список | pgsql-hackers |
On Wed, Mar 20, 2024 at 2:15 PM Jacob Champion <jacob.champion@enterprisedb.com> wrote: > 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 ) The thread got quiet, and I'm nervous that I squashed it unintentionally. :/ Is there consensus on whether the backoff is useful, even without the host tracking? (Or, alternatively, is the host tracking helpful in a way I'm not seeing?) Failing those, is there a way forward that could make it useful in the future? --Jacob
В списке pgsql-hackers по дате отправления: