X-Original-To: pgsql-docs-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id C6F30D1C91F for ; Fri, 8 Aug 2003 19:48:24 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 72042-06 for ; Fri, 8 Aug 2003 16:46:58 -0300 (ADT) Received: from varlena.com (adsl-64-165-208-112.dsl.snfc21.pacbell.net [64.165.208.112]) by svr1.postgresql.org (Postfix) with ESMTP id A2716D1C4CA for ; Fri, 8 Aug 2003 16:48:13 -0300 (ADT) Received: by varlena.com (Postfix on SuSE Linux 7.3 (i386), from userid 500) id 1D3C7394C7; Fri, 8 Aug 2003 12:42:13 -0700 (PDT) Date: Fri, 8 Aug 2003 12:42:13 -0700 From: elein To: pgsql-docs@postgresql.org, Tom Lane Cc: elein Subject: Re: Error message listing? Message-ID: <20030808124213.H31611@cookie> Mail-Followup-To: pgsql-docs@postgresql.org, Tom Lane References: <200308071604.19919.josh@agliodbs.com> <9659.1060298474@sss.pgh.pa.us> <15453.1060348911@sss.pgh.pa.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <15453.1060348911@sss.pgh.pa.us> User-Agent: Mutt/1.3.22.1i X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200308/45 X-Sequence-Number: 1905 The point of including the message texts is for people supporting various versions who are looking directly at the message texts for earlier versions. This also allows them to upgrade the error handling to use the new error codes instead of relying on the message text (which is what we want). elein On Fri, Aug 08, 2003 at 09:21:51AM -0400, Tom Lane wrote: > Peter Eisentraut writes: > > Tom Lane writes: > >> Or were you looking for src/include/utils/errcodes.h ? > > > I think we should put such a list in the documentation, at least for those > > error codes that we have really assigned. > > I have no objection to that. I have doubts about the utility of a > listing of message texts, but the SQLSTATE codes seem reasonable to > document. > > Would it be possible to generate the list automatically from errcodes.h, > to simplify future maintenance? > > regards, tom lane > > ---------------------------(end of broadcast)--------------------------- > TIP 7: don't forget to increase your free space map settings >