| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru> |
| Cc: | Евгений Ефимкин <efimkin(at)yandex-team(dot)ru>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Connection limit doesn't work for superuser |
| Date: | 2018-11-07 13:51:25 |
| Message-ID: | CA+TgmoZXD+yfhpaRViWeJxhz98NQ4ydCem=-1sySChV3C5mkBg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Nov 7, 2018 at 7:20 AM Andrey Borodin <x4mmm(at)yandex-team(dot)ru> wrote:
> >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.
I don't think we should consider something that prevents you from
connecting to the database to be in the same category as something
that limits what you can do once you are connected. IOW, +1 to the
original proposal from me.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2018-11-07 13:58:39 | Re: ATTACH/DETACH PARTITION CONCURRENTLY |
| Previous Message | John Naylor | 2018-11-07 13:47:59 | Re: valgrind on initdb |