| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Adam Brightwell <adam(dot)brightwell(at)crunchydatasolutions(dot)com> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Petr Jelinek <petr(at)2ndquadrant(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Additional role attributes && superuser review |
| Date: | 2015-01-19 13:33:27 |
| Message-ID: | CA+TgmoZo6HW4xukJ8KHVrebo8J69Fh-NG60rXFOk6LiyaKsOZQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Jan 15, 2015 at 6:03 PM, Adam Brightwell
<adam(dot)brightwell(at)crunchydatasolutions(dot)com> wrote:
> * ONLINE_BACKUP - allows role to perform backup operations
> - originally proposed as BACKUP - due to concern for the use of that term
> in relation to other potential backup related permissions this form is in
> line with the documentation as it describes the affected backup operations
> as being 'online backups'.
> - applies only to the originally proposed backup functions.
I'm slightly mystified as to how including the word "online" helps
here. It's unlikely that there will be an offline_backup permission,
because if the system is off-line, SQL-level permissions are
irrelevant.
> * LOG - allows role to rotate log files - remains broad enough to consider
> future log related operations
Maybe LOGFILE? Only because some confusion with the LOG message level
seems possible; or confusion about whether this is a permission that
lets you log things.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2015-01-19 13:36:55 | Re: A minor typo in brin.c |
| Previous Message | Alvaro Herrera | 2015-01-19 13:30:11 | Re: proposal: disallow operator "=>" and use it for named parameters |