| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "James B(dot) Byrne" <byrnejb(at)harte-lyne(dot)ca> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Problems with a custom LOCALE |
| Date: | 2012-12-14 22:40:27 |
| Message-ID: | 8460.1355524827@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"James B. Byrne" <byrnejb(at)harte-lyne(dot)ca> writes:
> PG::Error: ERROR: encoding "UTF8" does not match locale
> "en_CA(at)yyyy-mmm-dd(dot)UTF-8"
> DETAIL: The chosen LC_CTYPE setting requires encoding "LATIN1".
> : CREATE DATABASE "hll_th_forex_test" ENCODING = 'UTF8' TEMPLATE =
> "template1"
> I am constructing this remotely using a Rake task borrowed from Ruby
> on Rails 3.2.9 and employing ActiveRecord-3.2.9. We use a custom
> local on all our servers "en_CA(at)yyyy-mmm-dd(dot)UTF-8" which differs from
> en_CA only in the presentation of the date.
Sorta looks like you based that locale on an ISO 8859-1 locale, not a
UTF8 locale. AFAICT from looking at the code, PG is seeing that
nl_langinfo(CODESET) returns "ISO-8859-1" or some variant spelling,
so it complains.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Noel | 2012-12-15 05:02:39 | Re: initdb error |
| Previous Message | James B. Byrne | 2012-12-14 21:33:16 | Problems with a custom LOCALE |