From: Jonathan S. Katz <jkatz@postgresql.org>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Andy Dossett <dossett@btinternet.com>
Cc: Bruce Momjian <bruce@momjian.us>
Cc: pgsql-docs@lists.postgresql.org
Subject: Re: Appendix A. PostgreSQL Error Codes
Date: Sun, 29 Apr 2018 00:33:59 -0400
Message-ID: <31ADFE0E-37A4-4FF8-B18D-F8957F69A4E3@postgresql.org> (raw)
In-Reply-To: <3933.1524949881@sss.pgh.pa.us>
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>
> On Apr 28, 2018, at 5:11 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> "Andy Dossett" <dossett@btinternet.com> 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.
>
> 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 “see more info on "/support/sql-error-codes/“ or some URL.
The table on such a page could contain features such as:
- sortable by number vs. alphabetical
- “searchable” if needed (eliminate results)
- more information about what causes such errors, perhaps with an
example of the detailed message.
I don’t know if this would be helpful or not. Personally I’ve only looked
at the error codes section a handful of times, mostly out of curiosity or
experimenting with ORM/adapter type code.
Jonathan
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-docs@postgresql.org
Cc: jkatz@postgresql.org, tgl@sss.pgh.pa.us, dossett@btinternet.com, bruce@momjian.us, pgsql-docs@lists.postgresql.org
Subject: Re: Appendix A. PostgreSQL Error Codes
In-Reply-To: <31ADFE0E-37A4-4FF8-B18D-F8957F69A4E3@postgresql.org>
* 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