Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fCe2S-0005Ll-EW for pgsql-docs@arkaria.postgresql.org; Sun, 29 Apr 2018 04:34:16 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fCe2Q-0005qm-SL for pgsql-docs@arkaria.postgresql.org; Sun, 29 Apr 2018 04:34:14 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fCe2Q-0005qd-J8 for pgsql-docs@lists.postgresql.org; Sun, 29 Apr 2018 04:34:14 +0000 Received: from meldrar.postgresql.org ([2a02:c0:301:0:ffff::31]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fCe2M-00048B-Ui for pgsql-docs@lists.postgresql.org; Sun, 29 Apr 2018 04:34:13 +0000 Received: from pool-98-116-99-252.nycmny.fios.verizon.net ([98.116.99.252] helo=ph33r-retina.home) by meldrar.postgresql.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fCe2F-0004cN-AS; Sun, 29 Apr 2018 04:34:05 +0000 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Appendix A. PostgreSQL Error Codes From: "Jonathan S. Katz" In-Reply-To: <3933.1524949881@sss.pgh.pa.us> Date: Sun, 29 Apr 2018 00:33:59 -0400 Cc: Andy Dossett , Bruce Momjian , pgsql-docs@lists.postgresql.org Content-Transfer-Encoding: quoted-printable Message-Id: <31ADFE0E-37A4-4FF8-B18D-F8957F69A4E3@postgresql.org> References: <152482369232.19804.12598002996950785414@wrigleys.postgresql.org> <20180427133914.GB32454@momjian.us> <25849.1524842189@sss.pgh.pa.us> <000001d3dec8$16875630$43960290$@btinternet.com> <3933.1524949881@sss.pgh.pa.us> To: Tom Lane X-Mailer: Apple Mail (2.3273) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk > On Apr 28, 2018, at 5:11 PM, Tom Lane wrote: >=20 > "Andy Dossett" writes: >> The use case is pretty simple; my system has thrown an SQL error = code, I >> want to know what it means. >> Having the list in 'order by sqlstate' sequence would save me from = having to >> hunt up and down the list. And I can easily determine if the error = code is >> missing; I can then raise another bug report. >=20 > Hm ... I'm not finding that to be a very compelling argument. Reading = the > message text is usually *far* more illuminating, because the error = codes > are (in many cases) rather broad categories rather than exact = conditions. > For the use case of "why did I get this error", I'd say that looking = in > Appendix A is quite unhelpful, and sorting it differently wouldn't = make > it any more helpful. Is this information we might want to add to the main part of the = website? We could provide the list of error codes in Appendix A as is right now, reference to =E2=80=9Csee more info on "/support/sql-error-codes/=E2=80=9C= or some URL. The table on such a page could contain features such as: - sortable by number vs. alphabetical - =E2=80=9Csearchable=E2=80=9D if needed (eliminate results) - more information about what causes such errors, perhaps with an example of the detailed message. I don=E2=80=99t know if this would be helpful or not. Personally I=E2=80=99= ve only looked at the error codes section a handful of times, mostly out of curiosity = or experimenting with ORM/adapter type code. Jonathan=