misleading (or perhaps confusing) error messages

Dave E Martin (xxiii(at)cyberdude(dot)com) reports a bug with a severity of 3
The lower the number the more severe it is.

Short Description
misleading (or perhaps confusing) error messages

Long Description
When an error is generated as the result of a trigger (or other indirect action) it would be helpful if the error message could somehow indicate the trigger was the cause, rather than the executed statement itself.
<PRE>
for instance:

insert into NAS values (...);
ERROR: nas_make: Permission denied

</PRE>
While the error message is technically correct, it tends to leave one scratching one's head, until one remembers or realizes that a trigger was involved.
When dealing with a complicated series of statements and/or transactions it may be considerably more difficult to make the required inference from the error message.

Sample Code

No file was uploaded with this report