| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Dmitriy Igrishin <dmitigr(at)gmail(dot)com> |
| Cc: | Euler Taveira de Oliveira <euler(at)timbira(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: SQLSTATE of notice PGresult |
| Date: | 2010-09-22 10:27:21 |
| Message-ID: | AANLkTi=nP47gtNSC=gKuFzOxbCqcG6HrsCgLvsFqa7ft@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Sep 22, 2010 at 4:18 AM, Dmitriy Igrishin <dmitigr(at)gmail(dot)com> wrote:
> Okay, as Robert points, "00000" code in successful messages seems as waste
> of bytes. But according to the documentation, "All messages emitted by the
> PostgreSQL server are assigned five-character error codes that follow the
> SQL
> standard's conventions for "SQLSTATE" codes." - the first sentence of
> http://www.postgresql.org/docs/9.0/static/errcodes-appendix.html
Sounds like that wording needs some adjustment. I'm not even sure
that it would be correct to say "All error messages...", unless
elog(ERROR, "can't happen") throws something into that field.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stefan Kaltenbrunner | 2010-09-22 10:28:18 | Re: snapshot generation broken |
| Previous Message | Magnus Hagander | 2010-09-22 10:25:45 | Re: snapshot generation broken |