Received: from localhost (unknown [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id E146A2E01BD for ; Mon, 21 Jan 2008 21:21:50 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 70184-01 for ; Mon, 21 Jan 2008 21:21:46 -0400 (AST) Received: from weatherbeeta.com.au (unknown [218.214.212.154]) by postgresql.org (Postfix) with ESMTP id C22802E0165 for ; Mon, 21 Jan 2008 21:20:26 -0400 (AST) Received: (qmail 24598 invoked from network); 22 Jan 2008 01:20:23 -0000 X-NetworkBox-HamSign: 0101;OUT;wbeetaau1;6733edb565ad081de619415fe75d79d7; Received: from mail.weatherbeeta.com.au (10.20.0.2) by network-box.weatherbeeta.com.au with SMTP; 22 Jan 2008 01:20:23 -0000 Received: (qmail 16181 invoked by uid 1166); 22 Jan 2008 12:20:22 +1100 Received: from 172.20.0.155 by mail.weatherbeeta.com.au (envelope-from , uid 1165) with qmail-scanner-1.25-st-qms (clamdscan: 0.88.6/2315. perlscan: 1.25-st-qms. Clear:RC:1(172.20.0.155):. Processed in 0.258388 secs); 22 Jan 2008 01:20:22 -0000 X-Antivirus-mail.weatherbeeta.com.au-Mail-From: phillip.smith@weatherbeeta.com.au via mail.weatherbeeta.com.au X-Antivirus-mail.weatherbeeta.com.au: 1.25-st-qms (Clear:RC:1(172.20.0.155):. Processed in 0.258388 secs Process 16169) Received: from it-phil.weatherbeeta.com.au (HELO wbaus090) (172.20.0.155) by mail.weatherbeeta.com.au with SMTP; 22 Jan 2008 12:20:20 +1100 From: "Phillip Smith" To: "'Kevin Kempter'" , Subject: Re: pg_restore errors Date: Tue, 22 Jan 2008 12:20:18 +1100 Organization: Weatherbeeta Pty Ptd Message-ID: <01e501c85c94$f35ddff0$9b0014ac@wbaus090> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 Importance: Normal In-Reply-To: <200801211806.57989.kevin@kevinkempterllc.com> X-Scanned-By-wbeetaau1: Virus scan performed by network-box X-Scanned-By-wbeetaau1: Scanner file id is wbeetaau1-1200964823.747-24591-000 X-Scanned-By-wbeetaau1: No known viruses found in message (received+scanned in 0.01/0.03 secs) X-Scanned-By-wbeetaau1: Spam-Check-Result: No, hits=0 required=7 tests= autolearn=no version=2.0 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.72 tagged_above=0 required=5 tests=AWL=-0.777, BAYES_50=0.001, MIME_QP_LONG_LINE=1.396, RDNS_NONE=0.1 X-Spam-Level: X-Archive-Number: 200801/217 X-Sequence-Number: 27991 > Trying to restore a pg_dump I get this: >=20 > pg_restore: ERROR: invalid byte sequence for encoding "UTF8": 0xae > HINT: This error can also happen if the byte sequence does not match = the > encoding expected by the server, which is controlled by = "client_encoding". > CONTEXT: COPY imm_lookup, line 2 > pg_restore: [archiver (db)] error returned by PQendcopy: ERROR: = invalid > byte > sequence for encoding "UTF8": 0xae > HINT: This error can also happen if the byte sequence does not match = the > encoding expected by the server, which is controlled by = "client_encoding". > CONTEXT: COPY imm_lookup, line 2 I had a similar issue a week or 2 ago - turns out my original database = was using SQL_ASCII encoding, not UTF-8. Can your client tell you what encoding they're using? Otherwise, just = try a few different ones. Someone else might have a tricky way to work out = what the encoding should be based on the dump (but I don't ;)) Cheers, ~p THINK BEFORE YOU PRINT - Save paper if you don't really need to print this *******************Confidentiality and Privilege Notice******************* The material contained in this message is privileged and confidential to the addressee. If you are not the addressee indicated in this message or responsible for delivery of the message to such person, you may not copy or deliver this message to anyone, and you should destroy it and kindly notify the sender by reply email. Information in this message that does not relate to the official business of Weatherbeeta must be treated as neither given nor endorsed by Weatherbeeta. Weatherbeeta, its employees, contractors or associates shall not be liable for direct, indirect or consequential loss arising from transmission of this message or any attachments e-mail.