From: Christopher Kings-Lynne <chriskl@familyhealth.com.au>
To: Neil Conway <neilc@samurai.com>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Subject: Re: Upgrading the backend's error-message infrastructure
Date: Fri, 14 Mar 2003 10:51:24 +0800
Message-ID: <0d9901c2e9d4$9a3ad280$6500a8c0@fhp.internal> (raw)
References: <9168.1047588660@sss.pgh.pa.us>
<0cfd01c2e9cf$c16ea070$6500a8c0@fhp.internal>
<1047609869.357.1856.camel@tokyo>
> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: chriskl@familyhealth.com.au, neilc@samurai.com, pgsql-hackers@postgresql.org, tgl@sss.pgh.pa.us
Subject: Re: Upgrading the backend's error-message infrastructure
In-Reply-To: <0d9901c2e9d4$9a3ad280$6500a8c0@fhp.internal>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox