Re: Changing encoding

From: Ivo Rossacher <rossacher(at)bluewin(dot)ch>
To: pgsql-admin(at)postgresql(dot)org
Subject: Re: Changing encoding
Date: 2008-07-15 17:26:13
Message-ID: 200807151926.13848.rossacher@bluewin.ch
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

For the SQL_ASCII tables it depends what was actually written to the tables.
SQL_ASCII means that the server does not do any conversation and that the
client is responsible for the used encoding. So if there is data in the table
with different encodings (comming from different clients with different
encodings) you need to fix this by hand (depending on the data size an
editor, iconv, recode or similar might help you with this).
The Latin1 tables might be fixed by iconv or be autodetected by the server.

You can find details about the subject in the chapter 21.2 Character Set
Support of the server documentation.

Best regards
Ivo

Am Dienstag, 15. Juli 2008 16:14:25 schrieb Carol Walter:
> Hello,
>
> I have some databases that use SQL ASCII or Latin1 encoding that need
> to be UTF8. When I have drop the database and recreated it with the
> correct encoding I get errors in restoring the data. How is this done?
>
> Carol

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message samantha mahindrakar 2008-07-15 17:54:00 Jobs using pgagent
Previous Message Kevin Grittner 2008-07-15 17:24:10 Re: Backup and failover process