Re: Change postgresql encoding

From: Vincent Veyron <vv(dot)lists(at)wanadoo(dot)fr>
To: Oliver <ofabelo(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Change postgresql encoding
Date: 2015-02-09 14:01:07
Message-ID: 20150209150107.121ab2797f94cd2b8b510a12@wanadoo.fr
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-general

On Mon, 9 Feb 2015 08:11:25 +0000
Oliver <ofabelo(at)gmail(dot)com> wrote:

> 2015-02-09 7:52 GMT+00:00 Oliver <ofabelo(at)gmail(dot)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(dot)iso885915(at)euro
psql -c "ALTER DATABASE litigios set lc_time='es_ES(dot)iso885915(at)euro'" litigios

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

--
Salutations, Vincent Veyron

https://marica.fr/
Gestion des contentieux, des dossiers de sinistres assurance et des contrats pour le service juridique

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Oliver 2015-02-09 14:11:52 Re: Change postgresql encoding
Previous Message Marc Mamin 2015-02-09 13:02:06 Re: [PERFORM] <empty string> Vs NULL

Browse pgsql-general by date

  From Date Subject
Next Message Oliver 2015-02-09 14:11:52 Re: Change postgresql encoding
Previous Message Nicolas Paris 2015-02-09 12:45:38 Re: Change postgresql encoding