From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: NOTICE vs WARNING |
Date: | 2003-08-26 21:40:44 |
Message-ID: | 16751.1061934044@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> Well, there are plenty of NOTICE instances that carry a definite need to
> worry, such as identifier truncation, implicitly added FROM items,
> implicit changes to types specified as "opaque", unsupported and ignored
> syntax clauses.
Of course, some of those may be misclassified...
> I have a slight feeling that these two categories cannot usefully be
> distinguished, but I'm interested to hear other opinions.
I would say that NOTICEs are things that are routine in certain
contexts. We would not bother with the NOTICE at all if we thought
it held no interest, but often it doesn't have any.
Ignored syntax clauses probably ought to be WARNINGs, since the message
is telling you that what you asked for isn't going to be done. The
other examples you give seem appropriate as NOTICEs. In particular,
the notices about changing "opaque" types to something else are a
routine occurrence in upgrading old schemas, and so I think it's
reasonable for them to be NOTICEs.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Sullivan | 2003-08-26 21:56:39 | 2-phase commit |
Previous Message | Bruce Momjian | 2003-08-26 21:10:59 | Re: Networking in 7.4? |