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

From Alvaro Herrera
Subject Re: superuser() shortcuts
Date
Msg-id 20141126145340.GO1639@alvin.alvh.no-ip.org
Whole thread Raw
In response to Re: superuser() shortcuts  (Stephen Frost <sfrost@snowman.net>)
Responses Re: superuser() shortcuts  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: superuser() shortcuts  (Andres Freund <andres@2ndquadrant.com>)
List pgsql-hackers
Stephen Frost wrote:
> * Andres Freund (andres@2ndquadrant.com) wrote:
> > On 2014-11-26 08:33:10 -0500, Stephen Frost wrote:
> > > Doesn't that argument then apply to the other messages which I pointed
> > > out in my follow-up to Andres, where the detailed info is in the hint
> > > and the main error message is essentially 'permission denied'?
> > 
> > A permission error on a relation is easier to understand than one
> > for some abstract 'replication' permission.
> 
> The more I consider this and review the error message reporting policy,
> the more I feel that the original coding was wrong and that this change
> *is* the correct one to make.

+1.  I don't care for the idea of "not moving from main error message to
errdetail" -- the rationale seems to be that errdetail might be hidden,
lost, or otherwise not read by the user; if that is so, why do we have
errdetail in the first place?  We might as well just move all the
errdetails into the main message, huh?

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



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Follow up to irc on CREATE INDEX vs. maintenance_work_mem on 9.3
Next
From: "Timmer, Marius"
Date:
Subject: [PATCH] explain sortorder