From: | "Phoenix Kiula" <phoenix(dot)kiula(at)gmail(dot)com> |
---|---|
To: | "James B(dot) Byrne" <byrnejb(at)harte-lyne(dot)ca> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: pg_dump on local Windows, pg_restore on Linux? |
Date: | 2007-08-16 01:15:44 |
Message-ID: | e373d31e0708151815v63b929cdnb35f4cfee374a749@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 16/08/07, James B. Byrne <byrnejb(at)harte-lyne(dot)ca> wrote:
>
> Date: Wed, 15 Aug 2007 20:31:45 +0200
> From: "Leif B. Kristensen" <leif(at)solumslekt(dot)org>
> To: pgsql-general(at)postgresql(dot)org
> Subject: Re: pg_dump on local Windows, pg_restore on Linux?
> Message-ID: <200708152031(dot)45917(dot)leif(at)solumslekt(dot)org>
>
> On Wednesday 15. August 2007, Phoenix Kiula wrote:
> >
> >This is great info, thanks. Could you let me know how I could change
> >the global values of "LC_ALL"? I am on Linux too, just CentOS, but I
> >suppose it should be the same or similar?
>
> See: man local and man 1p locale and man 1p localedef and /etc/sysconfig/i18n
>
> Do NOT manually set LC_ALL on a CentOS system unless you know exactly what
> you are doing and what programs will be impacted. If set then LC_ALL
> overrides all of the individual LC_ settings.
>
Thanks. Here's my locale information:
> locale
LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=
Is this enough to run a pgsql database that is supposed to house utf-8
content? Or should I somehow make sure LC_ALL carries the value of
'en_US.UTF-8' as well? If not manually, how would I do it, and how can
I trace what other programs may be impacted. It sounds like an
impossible task given that many applications/servers run on this
machine, so I am hoping that either there is a workaround for
postgresql, or that postgresql will work with just the above
parameters as they are.
TIA!
From | Date | Subject | |
---|---|---|---|
Next Message | Trevor Talbot | 2007-08-16 01:24:38 | Re: Writing most code in Stored Procedures |
Previous Message | Steve Manes | 2007-08-16 00:53:44 | Re: Writing most code in Stored Procedures |