Re: Change postgresql encoding

Поиск
Список
Период
Сортировка
От Oliver
Тема Re: Change postgresql encoding
Дата
Msg-id CALQkqm_uRhjeDCAvQxjbFpkhZ5F262E0zGYXbKSfzXdvH29gVg@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Change postgresql encoding  (Vincent Veyron <vv.lists@wanadoo.fr>)
Список pgsql-general
2015-02-09 14:01 GMT+00:00 Vincent Veyron <vv.lists@wanadoo.fr>:
On Mon, 9 Feb 2015 08:11:25 +0000
Oliver <ofabelo@gmail.com> wrote:

> 2015-02-09 7:52 GMT+00:00 Oliver <ofabelo@gmail.com>:
>
> > regional configuration name not valid <<es_ES.latin9>>
> > SQL state: 42809
> >
> > I've tried es_ES.iso8859-15 and same error.

>
> If I set encoding to latin9, lc_collate and lc_ctype to 'C', database is
> created correctly, but I'm not sure if it is ok :-? I want have database
> with iso8859-15 encoding.
> My system has, when I run 'locale', the next:
>


The locale must be installed on your system (I work with Debian, so 'dpkg-reconfigure locales'; don't know for RHEL)

Here are the command I used in a similar situation:

#create a latin9 database on a UTF8 cluster:
createdb litigios -E LATIN9 -T template0 -l es_ES.iso885915@euro
psql -c "ALTER DATABASE litigios set lc_time='es_ES.iso885915@euro'" litigios

#load the data (here a latin9 encoded pg_dump)
export PGCLIENTENCODING=LATIN9;
psql -f /path/to/dump/file litigios


Thank you very much, it worked perfectly! (I were trying es_ES.iso885915 .. and it worked with es_ES.iso885915@euro).
Thanks.

Regards... 

В списке pgsql-general по дате отправления:

Предыдущее
От: Vincent Veyron
Дата:
Сообщение: Re: Change postgresql encoding
Следующее
От: David Evans
Дата:
Сообщение: Re: Stability of JSON textual representation