| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: NOTICE vs WARNING |
| Date: | 2003-09-03 22:45:15 |
| Message-ID: | 200309032245.h83MjFo09773@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Christopher Kings-Lynne wrote:
> > In fact, I like the criterion that a warning should be raised rather than
> > a notice if the effect of the command deviates from what the command
> > actually says. That puts the messages for serials, primary keys, drop
> > cascades clearly into notices, messages about missing, implicitly added,
> > or changed syntax clauses into warnings.
> >
> > I don't think the dump reload scenario is particularly important. After
> > all, psql or pg_restore don't act differently upon notice or warning, it's
> > just something that the user reads.
>
> WARNINGs don't cause transaction rollback, right? Cos if they did, changing
> NOTICEs to WARNINGs would cause pain.
No, only ERROR does transaction rollback.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2003-09-03 23:31:21 | Re: compile warnings in CVS HEAD? |
| Previous Message | Bruce Momjian | 2003-09-03 22:35:44 | Re: Unixware Patch (Was: Re: Beta2 Tag'd and Bundled ...) |