From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Simon Riggs <simon(at)2ndquadrant(dot)com> |
Subject: | Re: Additional role attributes && superuser review |
Date: | 2014-10-16 13:18:15 |
Message-ID: | 20141016131815.GU28859@tamriel.snowman.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
* Magnus Hagander (magnus(at)hagander(dot)net) wrote:
> On Oct 16, 2014 1:59 PM, "Stephen Frost" <sfrost(at)snowman(dot)net> wrote:
> > Once I understand what "include pg_dump" and "include pg_basebackup"
> > mean, I'd be happy to work on adding those.
>
> Include pg_basebackup would mean the replication protocol methods for base
> backup and streaming. Which is already covered by the REPLICATION flag.
Well, right. I had the impression there was some distinction that I
just wasn't getting.
> But in think it's somewhat useful to separate these. Being able to execute
> pg_stop_backup allows you to break somebody else's backup currently
> running, which pg_basebackup is safe against. So being able to call those
> functions is clearly a higher privilege than being able to use
> pg_basebackup.
Agreed.
Thanks!
Stephen
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2014-10-16 13:19:16 | Re: WIP: dynahash replacement for buffer table |
Previous Message | Simon Riggs | 2014-10-16 13:06:56 | Re: Additional role attributes && superuser review |