Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 45FD92E327D for ; Thu, 13 Dec 2007 16:10:25 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 79533-03 for ; Thu, 13 Dec 2007 16:10:17 -0400 (AST) Received: from mail21.bluewin.ch (mail21.bluewin.ch [195.186.18.66]) by postgresql.org (Postfix) with ESMTP id 28A7A2E2F39 for ; Thu, 13 Dec 2007 16:10:21 -0400 (AST) Received: from [192.168.1.74] (85.1.199.213) by mail21.bluewin.ch (Bluewin 7.3.121) id 471B45BE00ECDEF8 for pgsql-admin@postgresql.org; Thu, 13 Dec 2007 20:10:19 +0000 From: Ivo Rossacher To: pgsql-admin@postgresql.org Subject: Re: pg_restore error Date: Thu, 13 Dec 2007 21:10:19 +0100 User-Agent: KMail/1.9.6 (enterprise 20070904.708012) References: <200712131006.23925.kevin@kevinkempterllc.com> In-Reply-To: <200712131006.23925.kevin@kevinkempterllc.com> MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200712132110.19284.rossacher@bluewin.ch> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200712/94 X-Sequence-Number: 27611 Am Donnerstag, 13. Dezember 2007 18.06:23 schrieb Kevin Kempter: > Hi list; > > We're seeing this error whern trying to restore a pg_dump file: > > --------------------------------------------------------------------------- >------------------------------ pg_restore: ERROR: invalid byte sequence for > encoding "UTF8": 0x9f CONTEXT: COPY log_customer_api, line 4551 pg_restore: > [archiver (db)] error returned by PQendcopy: ERROR: invalid byte sequence > for encoding "UTF8": 0x9f CONTEXT: COPY log_customer_api, line 4551 > pg_restore: *** aborted because of error > --------------------------------------------------------------------------- >------------------------------ I got similar messages for several reasons: -Restore of data dump from an older server version on a newer one. The UTF8 handling was changed several times, where mostly the older servers did accept worng byte codings which newer servers do not anymore. -The server was created with an other encoding then the one which created the dump. -The dump was edited and with it some wrong encodings did enter. If you could provide some more details what happened I might come up with some more ideas. Best regards Ivo > > > Any thoughts? > > > Thx in advance > > /Kevin > > ---------------------------(end of broadcast)--------------------------- > TIP 3: Have you checked our extensive FAQ? > > http://www.postgresql.org/docs/faq