Peter Geoghegan <pe...@2ndquadrant.com> writes:
> On 29 September 2011 23:15, Tom Lane <t...@sss.pgh.pa.us> wrote:
>> Looks like I broke it here:
>> http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=1cb108efb0e60d87e4adec38e7636b6e8efbeb57
> Hmm. Although it was obvious to me that this was an internal error, I
> have to wonder what a novice would have made of it. Specifically, I
> wonder if there should be an INTERNAL_ERROR severity level, to
> explicitly advertise that you're not supposed to see this, and to help
> log analysis tools (including grep) bring these sorts of things to the
> DBA's attention, as they are surely much more severe than most errors
> seen in practice.
Well, the SQLSTATE for this sort of thing is already
ERRCODE_INTERNAL_ERROR. As to whether it's more severe than other
errors, I'm not convinced. It didn't crash, nor corrupt your data.
regards, tom lane
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
