From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Stephen Frost <sfrost(at)snowman(dot)net> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Simon Riggs <simon(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: ALTER SYSTEM for pg_hba.conf |
Date: | 2017-01-05 17:32:47 |
Message-ID: | CA+TgmoZnFbKCx87fSqY8dAmHQo+maMHJhCqXPBHcVU-+nhrHWg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Jan 5, 2017 at 12:28 PM, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
> Generally speaking, an ALTER DATABASE is unlikely to make the cluster
> fail to start. To be clear, I've only seen 1 or 2 cases and I'm not
> sure if, in those cases, they even fully understood how much can be
> changed through ALTER DATABASE or ALTER ROLE.
OK.
> My goal in those cases (and others where I come across installations
> with a lot of superusers) is typically to try and educate them as to
> just how close a superuser is to the unix user and recommend that they
> reconsider how they handle access privileges in the system (in
> particular, to try and get them to not have so many superusers and
> instead use other ways to give people access to what they need).
Makes sense.
> Of course, that tends to lead into things like "well, how do I make sure
> that user X has read rights on every table, always" or "how do I give
> someone the ability to terminate runaway queries that another user
> started." We've made progress there, but there's more to do still.
I agree!
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Jesper Pedersen | 2017-01-05 17:33:42 | Re: Microvacuum support for Hash Index |
Previous Message | Robert Haas | 2017-01-05 17:31:52 | Re: [sqlsmith] Crash reading pg_stat_activity |