Message-ID: <0d9901c2e9d4$9a3ad280$6500a8c0@fhp.internal>
From: "Christopher Kings-Lynne" <chriskl@familyhealth.com.au>
To: "Neil Conway" <neilc@samurai.com>
Cc: "PostgreSQL Hackers" <pgsql-hackers@postgresql.org>,
	"Tom Lane" <tgl@sss.pgh.pa.us>
References: <9168.1047588660@sss.pgh.pa.us>
	<0cfd01c2e9cf$c16ea070$6500a8c0@fhp.internal>
	<1047609869.357.1856.camel@tokyo>
Subject: Re: Upgrading the backend's error-message infrastructure
Date: Fri, 14 Mar 2003 10:51:24 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

> On Thu, 2003-03-13 at 21:16, Christopher Kings-Lynne wrote:
> > Would it be possible to do a command line app?
> >
> > bash$ pg_error 1200D
> > Severity: ERROR
> > Message: Division by zero
> > Detail:
> > Hint: Modify statement to prevent zeros appearing in denominators.
>
> Is there any benefit to having this over just including an index of
> error codes in the documentation?

It's quick and easy, especially when there's thousands of error codes.
Ideally, the pg_error app and the error code documentation should be
automatically generated...

You could have a built-in function: pg_print_error(text) returns text, then
the pg_error command line program could just call that, plus the user could
check up errors from within postgresql as well...

Chris