Re: Appendix A. PostgreSQL Error Codes

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Andy Dossett" <dossett(at)btinternet(dot)com>
Cc: "'Bruce Momjian'" <bruce(at)momjian(dot)us>, pgsql-docs(at)lists(dot)postgresql(dot)org
Subject: Re: Appendix A. PostgreSQL Error Codes
Date: 2018-04-28 21:11:21
Message-ID: 3933.1524949881@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

"Andy Dossett" <dossett(at)btinternet(dot)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

In response to

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message David G. Johnston 2018-04-28 21:19:10 Re: Isn't "publication" wrongly defined here?
Previous Message Tom Lane 2018-04-28 21:01:08 Re: Documentation for CommandComplete is incorrect for CREATE TABLE with server version 10.2