X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 449C29FB1F9 for ; Mon, 14 Aug 2006 19:51:53 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 15205-04 for ; Mon, 14 Aug 2006 19:51:44 -0300 (ADT) X-Greylist: delayed 00:08:43.472904 by SQLgrey- Received: from web57113.mail.re3.yahoo.com (web57113.mail.re3.yahoo.com [216.252.111.126]) by postgresql.org (Postfix) with SMTP id 80DB59FB1D2 for ; Mon, 14 Aug 2006 19:51:44 -0300 (ADT) Received: (qmail 72414 invoked by uid 60001); 14 Aug 2006 22:42:48 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=4AQAfDM7aB2YVswM++rigHb+6KbCAvHgUe0Scq7OsqI/Aco80g2ayE9BiJlMMlw+HqR70XRRhdx7LCEEOr8UGDBMLzE+SBm06jTYj9cW7Lo1xAE5mB8kfLMkkMBE1hOmFsbS3HRxEKuwBmvhSSRGvlQWadjINOH1gGBVt/xOYfg= ; Message-ID: <20060814224248.72408.qmail@web57113.mail.re3.yahoo.com> Received: from [64.237.4.140] by web57113.mail.re3.yahoo.com via HTTP; Mon, 14 Aug 2006 15:42:48 PDT Date: Mon, 14 Aug 2006 15:42:48 -0700 (PDT) From: Abu Mushayeed Subject: UTF8 Questions To: pgsql-admin@postgresql.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-584365002-1155595368=:57801" Content-Transfer-Encoding: 8bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=4.707 tagged_above=0 required=5 tests=DNS_FROM_RFC_ABUSE, DNS_FROM_RFC_POST, DNS_FROM_RFC_WHOIS, HTML_10_20, HTML_MESSAGE X-Spam-Level: **** X-Archive-Number: 200608/158 X-Sequence-Number: 22701 --0-584365002-1155595368=:57801 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit 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. 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. 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. 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. --0-584365002-1155595368=:57801 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: 8bit 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.
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.
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.

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. --0-584365002-1155595368=:57801--