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

From Alvaro Herrera
Subject Re: superuser() shortcuts
Date
Msg-id 20141023232302.GH1791@alvin.alvh.no-ip.org
Whole thread Raw
In response to Re: superuser() shortcuts  ("Brightwell, Adam" <adam.brightwell@crunchydatasolutions.com>)
Responses Re: superuser() shortcuts  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
Re: superuser() shortcuts  (Stephen Frost <sfrost@snowman.net>)
Re: superuser() shortcuts  (Stephen Frost <sfrost@snowman.net>)
List pgsql-hackers
Brightwell, Adam wrote:

> > 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."

Sure.

> As I started looking at this, there are multiple other places where
> these types of error messages occur (opclasscmds.c, user.c,
> postinit.c, miscinit.c are just a few), not just around the changes in
> this patch.  If we change them in one place, wouldn't it be best to
> change them in the rest?  If that is the case, I'm afraid that might
> distract from the purpose of this patch.  Perhaps, if we want to
> change them, then that should be submitted as a separate patch?

Yeah.  I'm just saying that maybe this patch should adopt whatever
wording we agree to, not that we need to change other places.  On the
other hand, since so many other places have adopted the different
wording, maybe there's a reason for it and if so, does anybody know what
it is.  But I have to say that it does look inconsistent to me.

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [BUGS] ltree::text not immutable?
Next
From: Robert Haas
Date:
Subject: Re: [PATCH] add ssl_protocols configuration option