From: | "J(dot) Manuel Velasco - UBILIBET" <tech(at)ubilibet(dot)com> |
---|---|
To: | "J(dot) Manuel Velasco - UBILIBET" <tech(at)ubilibet(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: change encoding |
Date: | 2008-05-13 15:37:27 |
Message-ID: | 4829B5B7.60106@ubilibet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hello,
Thanks for your quick replay, but I had other thing to do and I haven't
could check your hint before.
I started a new postgresql-8-3 installation. Set it up, ok
I have the idea to create the database and the role and then load the
pg_dump result from the other database. The old databse has encoding
LATIN2 so I try to create with this encoding and I get the message(*):
ERROR: la codificacion LATIN2 no coincide con la configuracion regional
del servidor es_es.UTF8
DETAIL: la configuracion regional LC_TYPE del servidor requiere la
codificacion UTF8
The command I try is:
postgres=# create database gestio_sl with template=template0 owner
webadmin encoding='latin2';
(*)That means more or less:
LATIN2 doesn't match with the regional configuration of the server
regional configuration requires UTF8 encoding
So, my question is how can i set the regional configuration of the
server to LATIN2
Thanks in advance.
Good luck!
Martijn van Oosterhout escribió:
> On Tue, May 13, 2008 at 09:00:49AM +0200, J. Manuel Velasco - UBILIBET wrote:
>
>> Hello,
>>
>> I have installed a new postgresql server and I need to recover an old
>> database on it.
>> The database I have to recover has LATIN2 as encoding and when i try to
>> restore it into the new one I get error messages due to encoding.
>> I have read that from pgsql8-3 is not possible to have different
>> encoding and since by default the encoding for postgres is UTF8 my doubt
>> is how can I restore the old database with no errors.
>>
>
> The encoding must match the collation, that's all. You don't say what
> you are recovering, but pg_dump emits a "SET client_encoding=latin2",
> right? In which case it should just work.
>
> If it's something else you need to show us exactly what the error
> message is.
>
> If you want everything connecting to the database to think it's latin2,
> do:
>
> ALTER DATABASE foo SET client_encoding=latin2;
>
> Have a nice day,
>
--
From | Date | Subject | |
---|---|---|---|
Next Message | Merlin Moncure | 2008-05-13 15:42:20 | Re: PG -v- MySQL |
Previous Message | Tom Lane | 2008-05-13 15:36:57 | Re: Making sure \timing is on |