From: Tom Lane <tgl@sss.pgh.pa.us>
To: 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: Sat, 28 Apr 2018 17:11:21 -0400
Message-ID: <3933.1524949881@sss.pgh.pa.us> (raw)
In-Reply-To: <000001d3dec8$16875630$43960290$@btinternet.com>
References: <152482369232.19804.12598002996950785414@wrigleys.postgresql.org>
<20180427133914.GB32454@momjian.us>
<25849.1524842189@sss.pgh.pa.us>
<000001d3dec8$16875630$43960290$@btinternet.com>
"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.
regards, tom lane
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: 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: <3933.1524949881@sss.pgh.pa.us>
* 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