Skip site navigation (1) Skip section navigation (2)

NOTICE vs WARNING resolution

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: NOTICE vs WARNING resolution
Date: 2003-10-01 22:26:30
Message-ID: Pine.LNX.4.44.0310020021420.2932-100000@peter.localdomain (view raw or flat)
Thread:
Lists: 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(at)gmx(dot)net


pgsql-hackers by date

Next:From: Marc G. FournierDate: 2003-10-01 22:28:50
Subject: Re: Lost mails
Previous:From: Joshua D. DrakeDate: 2003-10-01 22:23:16
Subject: Re: Thoughts on maintaining 7.3

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group