Re: NOTICE vs WARNING - Mailing list pgsql-hackers

From Christopher Kings-Lynne
Subject Re: NOTICE vs WARNING
Date
Msg-id 04f701c371bd$2360cd10$2800a8c0@mars
Whole thread Raw
In response to Re: NOTICE vs WARNING  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: NOTICE vs WARNING
List pgsql-hackers
> 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.

Chris



pgsql-hackers by date:

Previous
From: "Christopher Kings-Lynne"
Date:
Subject: Re: Win32 native port
Next
From: Hans-Jürgen Schönig
Date:
Subject: Re: Is it a memory leak in PostgreSQL 7.4beta?