Re: superuser() shortcuts - Mailing list pgsql-hackers

From Brightwell, Adam
Subject Re: superuser() shortcuts
Date
Msg-id CAKRt6CQkH9Lb8dLApFkaW6EgLeuskeg1cn-9J6N0SbOLowQnXw@mail.gmail.com
Whole thread Raw
In response to Re: superuser() shortcuts  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: superuser() shortcuts
List 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.brightwell@crunchydatasolutions.com
Database Engineer - www.crunchydatasolutions.com



pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: idea: allow AS label inside ROW constructor
Next
From: David Johnston
Date:
Subject: Re: idea: allow AS label inside ROW constructor