From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Peter Geoghegan <peter(at)2ndquadrant(dot)com> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: "no relation entry for relid 1" |
Date: | 2011-09-29 23:21:04 |
Message-ID: | 23437.1317338464@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Peter Geoghegan <peter(at)2ndquadrant(dot)com> writes:
> On 29 September 2011 23:15, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2011-09-30 01:07:42 | Re: PostGre compatible to RHEL 6.1 |
Previous Message | Peter Geoghegan | 2011-09-29 22:50:13 | Re: "no relation entry for relid 1" |