| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Eugene Pimenov <libc(at)me(dot)com> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #4563: Translation of errors. |
| Date: | 2008-12-06 16:55:11 |
| Message-ID: | 493AAE6F.4040500@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Tom Lane wrote:
> "Eugene Pimenov" <libc(at)me(dot)com> writes:
>> 2) Write a code to every translation (e.g. Error 424242 inccorrect ...), so
>> people can actually google out a solution for their problems.
>
> RTFM:
> http://www.postgresql.org/docs/8.3/static/errcodes-appendix.html
PostgreSQL error codes are not as unique as the error messages.
If you don't like translated error messages, you could just set
lc_messages to en_US in your postgresql.conf.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2008-12-06 23:02:05 | Re: BUG #3818: Cross compilation problems |
| Previous Message | Fujii Masao | 2008-12-06 04:29:10 | Re: BUG #4566: pg_stop_backup() reports incorrect STOP WAL LOCATION |