From: | Rich Shepard <rshepard(at)appl-ecosys(dot)com> |
---|---|
To: | "pdxpug(at)postgresql(dot)org" <pdxpug(at)postgresql(dot)org> |
Subject: | Re: Next: Encoding Issue |
Date: | 2009-02-03 15:09:21 |
Message-ID: | alpine.LNX.2.00.0902030653590.9977@salmo.appl-ecosys.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pdxpug |
On Mon, 2 Feb 2009, Ewan, Michael wrote:
> In the shell environment
> export LC_ALL=C
> This will often fix many locale ills.
Michael,
I went one step further. In ~/.bash_profile I added:
export LC_ALL=
export LANG=en_US.utf8
then sourced the file. Now locale reports:
LANG=en_US.utf8
LC_CTYPE="en_US.utf8"
LC_NUMERIC="en_US.utf8"
LC_TIME="en_US.utf8"
LC_COLLATE=C
LC_MONETARY="en_US.utf8"
LC_MESSAGES="en_US.utf8"
LC_PAPER="en_US.utf8"
LC_NAME="en_US.utf8"
LC_ADDRESS="en_US.utf8"
LC_TELEPHONE="en_US.utf8"
LC_MEASUREMENT="en_US.utf8"
LC_IDENTIFICATION="en_US.utf8"
LC_ALL=
but this does not resolve the issue. I still see:
createdb: database creation failed: ERROR: encoding UTF8 does not match
server's locale en_US
DETAIL: The server's LC_CTYPE setting requires encoding LATIN1.
Setting LC_ALL=en_US.utf8 doesn't make any difference.
Any thoughts?
Rich
--
Richard B. Shepard, Ph.D. | Integrity Credibility
Applied Ecosystem Services, Inc. | Innovation
<http://www.appl-ecosys.com> Voice: 503-667-4517 Fax: 503-667-8863
From | Date | Subject | |
---|---|---|---|
Next Message | Selena Deckelmann | 2009-02-03 15:50:23 | Re: Next: Encoding Issue |
Previous Message | Rich Shepard | 2009-02-03 14:14:08 | Re: Dropping Old Databases |