| From: | "Brightwell, Adam" <adam(dot)brightwell(at)crunchydatasolutions(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: superuser() shortcuts |
| Date: | 2014-10-23 15:52:28 |
| Message-ID: | CAKRt6CQkH9Lb8dLApFkaW6EgLeuskeg1cn-9J6N0SbOLowQnXw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro,
> I noticed something strange while perusing this patch, but the issue
> predates the patch. Some messages say "must be superuser or replication
> role to foo", but our longstanding practice is to say "permission denied
> to foo". Why do we have this inconsistency? Should we remove it? If
> we do want to keep the old wording this patch should use "permission
> denied to" in the places that it touches.
If we were to make it consistent and use the old wording, what do you
think about providing an "errhint" as well?
Perhaps for example in slotfuncs.c#pg_create_physical_replication_stot:
errmsg - "permission denied to create physical replication slot"
errhint - "You must be superuser or replication role to use replication slots."
-Adam
--
Adam Brightwell - adam(dot)brightwell(at)crunchydatasolutions(dot)com
Database Engineer - www.crunchydatasolutions.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Johnston | 2014-10-23 16:03:28 | Re: idea: allow AS label inside ROW constructor |
| Previous Message | Andrew Dunstan | 2014-10-23 15:51:27 | Re: idea: allow AS label inside ROW constructor |