From: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
---|---|
To: | "Peter Eisentraut" <peter_e(at)gmx(dot)net>, "PostgreSQL Development" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: NOTICE vs WARNING |
Date: | 2003-08-26 00:49:40 |
Message-ID: | 083201c36b6b$ef063520$2800a8c0@mars |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Surely a WARNING is a problem that you should probably fix? Or at least pay
attention to. My thought is that you could turn of NOTICES and not worry.
(Which is what I sometimes do during restore, etc.)
Chris
----- Original Message -----
From: "Peter Eisentraut" <peter_e(at)gmx(dot)net>
To: "PostgreSQL Development" <pgsql-hackers(at)postgresql(dot)org>
Sent: Tuesday, August 26, 2003 12:44 AM
Subject: [HACKERS] NOTICE vs WARNING
> Can someone explain in succinct and general terms what the difference
> between a NOTICE and a WARNING is? I'm currently examining the validity
> of notice and warning messages throughout the backend, but I find these
> categories to be applied inconsistently.
>
> --
> Peter Eisentraut peter_e(at)gmx(dot)net
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index scan if your
> joining column's datatypes do not match
>
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2003-08-26 03:52:27 | Re: backwards-compat problem? |
Previous Message | Christopher Kings-Lynne | 2003-08-26 00:48:17 | Re: I am back |