| 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 14:00:55 |
| Message-ID: | alpine.LNX.2.00.0902030556220.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.
Thanks for the suggestion, Michael, but it didn't help here. Perhaps I
should try changing the locale setting to en_US.utf8.
I've not encountered this issue before. When I listed existing databases
(including the three I dropped yesterday as legacies of applications that
didn't make the grade), I saw that two (created by sql-ledger and me are
encoded LATIN1, the three encoded by the former apps were US_ASCII, and the
four owned by postgres (including the templates) are encoded UTF8.
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 | Rich Shepard | 2009-02-03 14:06:11 | Re: Next: Encoding Issue |
| Previous Message | Ewan, Michael | 2009-02-03 06:01:38 | Re: Dropping Old Databases |