| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Tom Dunstan" <pgsql(at)tomd(dot)cc> |
| Cc: | "Peter Eisentraut" <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: unclear enum error messages |
| Date: | 2007-11-29 05:32:18 |
| Message-ID: | 2600.1196314338@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Tom Dunstan" <pgsql(at)tomd(dot)cc> writes:
> I wouldn't get too worried, though. These are defensive error messages
> that are really just checking for sane input, and they seem difficult
> to deliberately trip, let alone accidentally, so stressing about them
> is probably unnecessary.
Right. I'm not really expecting to see that message fire; it's just
there to ensure sane behavior if it does happen. Peter might be right
that an elog instead of ereport would be sufficient.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2007-11-29 05:39:30 | Re: [HACKERS] [GENERAL] plperl and regexps with accented characters - incompatible? |
| Previous Message | Tom Dunstan | 2007-11-29 05:28:13 | Re: unclear enum error messages |