| From: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | "Neil Conway" <nconway(at)klamath(dot)dyndns(dot)org>, "PostgreSQL Hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: error codes |
| Date: | 2002-07-18 01:57:56 |
| Message-ID: | GNELIHDDFBOCMGBFGEFOOEDECDAA.chriskl@familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tatsuo Ishii | 2002-07-18 02:04:29 | CREATE CONVERSION mostly works now |
| Previous Message | Tom Lane | 2002-07-18 01:47:40 | Re: Planner very slow on same query to slightly different tables |