| From: | nconway(at)klamath(dot)dyndns(dot)org (Neil Conway) |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: error codes |
| Date: | 2002-07-17 20:17:58 |
| Message-ID: | 20020717201758.GA6846@klamath.dyndns.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jul 17, 2002 at 03:57:56PM -0400, Tom Lane wrote:
> nconway(at)klamath(dot)dyndns(dot)org (Neil Conway) writes:
> > Should every elog() have an error code?
>
> I believe we decided that it'd be okay to use one or two codes defined
> like "internal error", "corrupted data", etc for all the elogs that are
> not-supposed-to-happen conditions.
Ok, makes sense to me.
> > How should the backend code signal an error with an error number?
>
> Please read some of the archived discussions about this. All the points
> you mention have been brought up before.
Woops -- I wasn't aware that this had been discussed before, my apologies.
I'm reading the archives now...
Peter: are you planning to implement this?
Cheers,
Neil
--
Neil Conway <neilconway(at)rogers(dot)com>
PGP Key ID: DB3C29FC
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Richard Tucker | 2002-07-17 21:45:53 | Re: Issues Outstanding for Point In Time Recovery (PITR) |
| Previous Message | Tom Lane | 2002-07-17 19:57:56 | Re: error codes |