| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-docs(at)postgresql(dot)org |
| Subject: | Re: Error message listing? |
| Date: | 2003-08-07 23:33:55 |
| Message-ID: | 200308071633.55336.josh@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
Tom,
> Or were you looking for src/include/utils/errcodes.h ?
More or less.
The issue is that many projects have internal code to handle PG error messages
by parsing them for certain text. The overhaul of message handling is going
to break that code; users need to know what the new messages and/or codes are
before migrating.
--
-Josh Berkus
______AGLIO DATABASE SOLUTIONS___________________________
Josh Berkus
Complete information technology josh(at)agliodbs(dot)com
and data management solutions (415) 565-7293
for law firms, small businesses fax 621-2533
and non-profit organizations. San Francisco
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2003-08-08 07:29:07 | Re: Error message listing? |
| Previous Message | Tom Lane | 2003-08-07 23:21:14 | Re: Error message listing? |