> Should every elog() have an error code? I'm not sure -- there are many > elog() calls that will never been seen by the user, since the error > they represent will be caught before control reaches the elog (e.g. > parse errors, internal consistency checks, multiple elog(ERROR) > for the same user error, etc.) Perhaps for those error messages > that don't have numbers, we could just give them ERRNO_UNKNOWN or > a similar constant.
It might be cool to a little command utility "pg_error" or whatever that you pass an error code to and it prints out a very detailed description of the problem... Chris ---------------------------(end of broadcast)--------------------------- TIP 6: Have you searched our list archives? http://archives.postgresql.org