| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Stephen Frost <sfrost(at)snowman(dot)net>, Florian Pflug <fgp(at)phlo(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Streaming replication as a separate permissions |
| Date: | 2011-01-06 04:59:00 |
| Message-ID: | 1294289940.3243.3.camel@vanquo.pezone.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On tis, 2011-01-04 at 22:24 -0500, Robert Haas wrote:
> > Just to be clear: are we saying that "CREATE ROLE foo SUPERUSER"
> > should grant both superuser and replication, as well as the default
> > "postgres" user also having replication as well?
>
> I think that's what we're saying.
So now superusers have it by default but you can explicitly revoke it?
I guess that's still inconsistent with other superuser behavior. You
can't revoke a superuser's CREATEDB bit, for example. (You can, but it
won't have an effect, of course.)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2011-01-06 05:13:35 | Re: Problem with pg_upgrade (8.4 -> 9.0) due to ALTER DATABASE SET ROLE |
| Previous Message | Peter Eisentraut | 2011-01-06 04:55:11 | Re: Streaming replication as a separate permissions |