| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Peter Geoghegan <peter(at)2ndquadrant(dot)com> |
| Cc: | David Johnston <polobo(at)yahoo(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: enhanced error fields |
| Date: | 2012-12-28 20:30:58 |
| Message-ID: | 50DE0182.1080406@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 12/10/12 4:23 PM, Peter Geoghegan wrote:
> Well, this is an area that the standard doesn't have anything to say
> about. The standard defines errcodes, but not what fields they make
> available. I suppose you could say that the patch proposes that they
> become a Postgres extension to the standard.
The standard certainly does define extra fields for errors; see <get
diagnostics statement>. We have a GET DIAGNOSTICS statement in
PL/pgSQL, so there is certainly precedent for all of this.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alastair Turner | 2012-12-28 20:33:03 | Re: Submission Review: User control over psql error stream |
| Previous Message | Pavel Stehule | 2012-12-28 19:55:52 | Re: enhanced error fields |