pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Ivo Rossacher <rossacher@bluewin.ch>
To: pgsql-admin@postgresql.org
Subject: Re: UTF8 Questions
Date: Tue, 15 Aug 2006 04:16:18 +0200
Message-ID: <200608150416.18953.rossacher@bluewin.ch> (raw)
In-Reply-To: <20060814224248.72408.qmail@web57113.mail.re3.yahoo.com>
References: <20060814224248.72408.qmail@web57113.mail.re3.yahoo.com>

Am Dienstag, 15. August 2006 00.42 schrieb Abu Mushayeed:
> We upgraded our Db from LATIN1 to UTF8 as follows:
>
> 1. new install with encoding=UTF8
> 2. pg_dump from old DB and import into new db using psql as follows:
>  pg_dump out of old_db|psql into new_db
> 3. New feeds (data files) come in same as when the DB was latin1. If error
> message from any load script like "Invalid UTF8 code ...",  then, "set
> client_encoding=latin1" in the script and run again and all is well. 

So most probably the dump is latin1 (this was the clientencoding during 
dumping).

> 4. all 
> the other scripts run on the UTF8 Db as is and no errors, meaning the
> scripts has not been changed and is running as is before when DB was
> latin1. 

That there is no error message does not mean that there is no error in the 
encoding. It only means that there is no Invalid UTF8. So it is importent to 
set the correct client encoding, which was used for the backup, also during 
restore.

> 5. Now, some of the DB feeds (data files) is changing to UTF8. What 
> needs to be done when the data feeds changes to UTF8.

When you plan to insert non Latin1 codes into the database you have to change 
the clientencoding for backup/restore to UTF8.

Have a look at chapter 20 of the manual for different possibilies to set the 
client encoding.

Best regards
Ivo
>
> Any other thoughts or if there is a problem that anyone sees, please help
> me with a solution.
>
> Thanks
>
>
> ---------------------------------
> Talk is cheap. Use Yahoo! Messenger to make PC-to-Phone calls.  Great rates
> starting at 1ยข/min.



view thread (2+ messages)

Message-ID: <200608150416.18953.rossacher@bluewin.ch>
Permalink:  ../200608150416.18953.rossacher@bluewin.ch/
Also on:    postgresql.org/message-id/200608150416.18953.rossacher@bluewin.ch

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: rossacher@bluewin.ch
  Subject: Re: UTF8 Questions
  In-Reply-To: <200608150416.18953.rossacher@bluewin.ch>
  References: <20060814224248.72408.qmail@web57113.mail.re3.yahoo.com> <200608150416.18953.rossacher@bluewin.ch>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox