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 [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073 ---------------------------(end of broadcast)--------------------------- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
