| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Theodore Petrosky <tedpet5(at)yahoo(dot)com> |
| Cc: | pgsql-sql(at)postgresql(dot)org, Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Subject: | Re: case sensitive/insensitive confusion |
| Date: | 2005-02-01 18:36:14 |
| Message-ID: | 16248.1107282974@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
Theodore Petrosky <tedpet5(at)yahoo(dot)com> writes:
> Mac os x, postgresql 8.0.1
> initdb --locale=es_ES ~/testdb
> ...
> The database cluster will be initialized with locale es_ES.
> initdb: could not find suitable encoding for locale "es_ES"
> Rerun initdb with the -E option.
I looked into this and find that the issue seems to be Apple's rather
limited (not to say brain dead) locale support. What I see on OSX
10.3.7 is that <langinfo.h> defines CODESET, but nl_langinfo(CODESET)
always returns an empty string. So there's not any obvious way to
determine the correct encoding associated with a locale setting.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joel Fradkin | 2005-02-01 19:23:15 | Re: MSSQL versus Postgres timing |
| Previous Message | Bricklen Anderson | 2005-02-01 17:25:41 | Re: MSSQL versus Postgres timing |