| From: | Guillaume Smet <guillaume(dot)smet(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: SQL state in log_line_prefix |
| Date: | 2009-05-10 14:21:14 |
| Message-ID: | 1d4e0c10905100721o5d73cbdcp706d528078cca5d8@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, May 10, 2009 at 4:07 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> This might or might not be worth doing, but it seems pretty nearly
> entirely useless for the claimed purpose. What is your division between
> "user errors" and "system errors", and how will the SQLSTATE help you
> make that?
We use http://www.postgresql.org/docs/8.3/interactive/errcodes-appendix.html
to sort the errors.
For example:
Class 22 — Data Exception -> user
Class 53 — Insufficient Resources -> system
Class XX — Internal Error -> system
It's not perfect but it's the best way we found to classify them at the moment.
--
Guillaume
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2009-05-10 15:11:39 | Re: Implementation of GROUPING SETS (T431: Extended grouping capabilities) |
| Previous Message | Tom Lane | 2009-05-10 14:07:55 | Re: SQL state in log_line_prefix |