Re: Connection limit doesn't work for superuser

From: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>
To: Evgeniy Efimkin <efimkin(at)yandex-team(dot)ru>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Connection limit doesn't work for superuser
Date: 2018-11-07 12:19:50
Message-ID: 47C328D4-8382-4AC4-A7B7-BEF2CB19D6CE@yandex-team.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi!

> 7 нояб. 2018 г., в 11:48, Evgeniy Efimkin <efimkin(at)yandex-team(dot)ru> написал(а):
> It would be nice if ALTER USER ... WITH CONNECTION LIMIT will work for superuser. It would protect against connection leaks. e.g. we have two superusers, one of them reached connection limit but not max_connections, the other is still possible to connect to database and solve the problem. The current behaviour would be the same for the case with rolconnlimit = -1. Superuser can execute NOLOGIN to another superuser and it works. I found previos discussion about CONNECTION LIMIT for superuser but it ended about Slony. https://www.postgresql.org/message-id/1154351265.22367.210.camel%40coppola.muc.ecircle.de
>

Current docs contain following description for SUPERUSER:
>These clauses determine whether the new role is a “superuser”, who can override all access restrictions within the database.
Do we consider connection limit "access restriction"? Superuser can avoid setting his connection limit if he do not need it.

Best regards, Andrey Borodin.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jesper Pedersen 2018-11-07 12:26:28 Re: pread() and pwrite()
Previous Message David Rowley 2018-11-07 11:46:54 Re: Speeding up INSERTs and UPDATEs to partitioned tables