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

From Stephen Frost
Subject Re: superuser() shortcuts
Date
Msg-id 20141126151820.GZ28859@tamriel.snowman.net
Whole thread Raw
In response to Re: superuser() shortcuts  (Andres Freund <andres@2ndquadrant.com>)
Responses Re: superuser() shortcuts  (Andres Freund <andres@2ndquadrant.com>)
List pgsql-hackers
* Andres Freund (andres@2ndquadrant.com) wrote:
> I don't see how you read the contrary from the guidelines:
> > The primary message should be short, factual, and avoid reference to
> > implementation details such as specific function names. "Short" means
> > "should fit on one line under normal conditions". Use a detail message
> > if needed to keep the primary message short, or if you feel a need to
> > mention implementation details such as the particular system call that
> > failed. Both primary and detail messages should be factual. Use a hint
> > message for suggestions about what to do to fix the problem, especially
> > if the suggestion might not always be applicable.  It's quite common
> > that you'll only see the actual error message in logs and displayed
> > error messages.

Having to be the owner of a relation to TRUNCATE it was an
implementation detail, and one which changed back in 2008.

Needing to have the replication role attribute is an implementation
detail.  It's not the error- the error is *permission denied to do X*.
Thanks,
    Stephen

pgsql-hackers by date:

Previous
From: Palle Girgensohn
Date:
Subject: Re: [pgsql-packagers] Palle Girgensohn's ICU patch
Next
From: Alvaro Herrera
Date:
Subject: Re: no test programs in contrib