NOTICE vs WARNING resolution - Mailing list pgsql-hackers

From Peter Eisentraut
Subject NOTICE vs WARNING resolution
Date
Msg-id Pine.LNX.4.44.0310020021420.2932-100000@peter.localdomain
Whole thread Raw
List pgsql-hackers
Following up to the discussion a few weeks ago and in accordance with the
criteria developed there about how a message should be classified NOTICE
or WARNING, I have identified the following cases that ought to be
reclassified:

change WARNING to NOTICE:

table "%s" has no indexes  [during REINDEX]

change NOTICE to WARNING:

changing return type of function %s from "opaque" to xxx
INTERVAL(%d) precision reduced to maximum allowed, %d

I also thought that

copyObject() failed to produce an equal parse tree

should be made an elog() because it's an internal error.


Objections?

-- 
Peter Eisentraut   peter_e@gmx.net



pgsql-hackers by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: Re: Thoughts on maintaining 7.3
Next
From: "Marc G. Fournier"
Date:
Subject: Re: Lost mails