Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id ED2AD2E01D4 for ; Sat, 5 Jan 2008 06:15:21 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 95353-01 for ; Sat, 5 Jan 2008 06:15:19 -0400 (AST) Received: from web90515.mail.mud.yahoo.com (web90515.mail.mud.yahoo.com [216.252.100.182]) by postgresql.org (Postfix) with SMTP id E233C2E01C6 for ; Sat, 5 Jan 2008 06:15:18 -0400 (AST) Received: (qmail 56961 invoked by uid 60001); 5 Jan 2008 10:15:17 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=ZuVMS9yZBedG+yNSO6uegkgZ4ONFsipvF4CNB/xPeQe7xH27WqZSuPyv4lsv8VnWBO4A8I5L/VqyBhbqG4N7hmClGLz0pWBmAqrRyCYhLPNYClcvKXR1Rrhk5OVSZd72QWJ85RObEbtH2aubbj+79HP2i21SfRSravqrTp+7UD4=; X-YMail-OSG: dvYhi68VM1lczeg9jIpGnQpePJeqLpe9r1pL4.d7oLXcOBQ0QveBVeS5Qh0IKqFG2IucvXEzZdOMXfx2d_lpv6HCw79VzkE5cJqcFDWEK1lchMl1iJjjLUvuCAi1Uw-- Received: from [86.125.58.1] by web90515.mail.mud.yahoo.com via HTTP; Sat, 05 Jan 2008 02:15:17 PST Date: Sat, 5 Jan 2008 02:15:17 -0800 (PST) From: Popovici Alexandru Subject: Re: invalid byte sequence for encoding "UNICODE":0xa1 To: pgsql-admin@postgresql.org In-Reply-To: <200801050156.04303.rossacher@bluewin.ch> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Message-ID: <587115.55757.qm@web90515.mail.mud.yahoo.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200801/71 X-Sequence-Number: 27845 Thank you for your answer. I tryed to restore the dump file ( some data was deleted an need it to be restored ) on the same server on which was made (windows 2003 ), using the same software ( pgAmin ) used at backup. I have not change any settings for PostgreSQL server or pgAdmin. The data is not corupted because I succeded to restore it on a different computer on which I have installed the PostgreSQL and PgAmin 1.2. But I can do this on production server. > There are serveral possible reasons for this issue. > -Restoring on a newer server then the backup was > taken from. The servers got > pickier regarding encoding over several versions. > -Restoring on a server with diverent encoding then > the encoding of the server > where the backup came from. > -Restoring with a differen client encoding at the > pgAdmin (probably different > version or setting). > -Corruptet data file. > -... > ____________________________________________________________________________________ Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ