Received: from localhost (maia-3.hub.org [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id F17FC9F9F46 for ; Tue, 12 Dec 2006 05:57:43 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-new, port 10024) with ESMTP id 77335-08 for ; Tue, 12 Dec 2006 05:57:32 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.4 Received: from nz-out-0102.google.com (nz-out-0506.google.com [64.233.162.229]) by postgresql.org (Postfix) with ESMTP id AED8B9F9EED for ; Tue, 12 Dec 2006 05:57:35 -0400 (AST) Received: by nz-out-0102.google.com with SMTP id i11so926578nzh for ; Tue, 12 Dec 2006 01:57:34 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=c8EBntBVqqSPSwdbovwB0iVNxjFo0IHaM2du1IjPnEdLgPsQprqEOJUOZKWvTqE60RIJDiM5/OZpv20rDvr+ReD+UBUV4B8w72M/ued5YokNXUO/JjE2qrfeDMd3xaZLUN8rL08Cywd6z8xj3DY4PrN6TvdLsgJ3fltbHihvGOA= Received: by 10.64.10.2 with SMTP id 2mr12819621qbj.1165917454293; Tue, 12 Dec 2006 01:57:34 -0800 (PST) Received: by 10.65.206.18 with HTTP; Tue, 12 Dec 2006 01:57:34 -0800 (PST) Message-ID: Date: Tue, 12 Dec 2006 14:57:34 +0500 From: "Shoaib Mir" To: "Manuel Trujillo" Subject: Re: Migration problems with encoding. Cc: pgsql-admin@postgresql.org In-Reply-To: <457E7AC9.9010101@vlex.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_69737_15297534.1165917454189" References: <457E7AC9.9010101@vlex.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200612/154 X-Sequence-Number: 23946 ------=_Part_69737_15297534.1165917454189 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Have you tried using 'iconv' for cleaning up the invalid UTF8 character? In case of big files you can always split them. ----------------- Shoaib Mir EnterpriseDB (www.enterprisedb.com) On 12/12/06, Manuel Trujillo wrote: > > Hi! > > Firs, I will apologize about my bad english... sorry... > > I have a database in postgres 8.0 with encoding defined with UTF8. All > work fine, but because the new features from 8.2 version, we would like > to migrate the database to this new version. > The problem: Encoding incompatibilities between the postgresql version. > > How can i resolve this with a database about 16 Gb? Are there any > document about how to solve this? > > Thank you very much. > > -- > Manuel Trujillo Albarral > Responsable de Sistemas > VLEX NETWORKS S.L. > Telf: 93-272.26.85 ext. 111 > Jabber/GoogleTalk manu.trujillo@gmail.com > http://www.vlex.com > > ---------------------------(end of broadcast)--------------------------- > TIP 6: explain analyze is your friend > ------=_Part_69737_15297534.1165917454189 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Have you tried using 'iconv' for cleaning up the invalid UTF8 character? In case of big files you can always split them.

-----------------
Shoaib Mir
EnterpriseDB (www.enterprisedb.com )

On 12/12/06, Manuel Trujillo <mtrujillo@vlex.com> wrote:
Hi!

Firs, I will apologize about my bad english... sorry...

I have a database in postgres 8.0 with encoding defined with UTF8. All
work fine, but because the new features from 8.2 version, we would like
to migrate the database to this new version.
The problem: Encoding incompatibilities between the postgresql version.

How can i resolve this with a database about 16 Gb? Are there any
document about how to solve this?

Thank you very much.

--
Manuel Trujillo Albarral
Responsable de Sistemas
VLEX NETWORKS S.L.
Telf: 93-272.26.85  ext. 111
Jabber/GoogleTalk manu.trujillo@gmail.com
http://www.vlex.com

---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend

------=_Part_69737_15297534.1165917454189--