Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 50169650739 for ; Thu, 10 Jul 2008 23:56:53 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 67305-07 for ; Thu, 10 Jul 2008 23:56:43 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.30]) by postgresql.org (Postfix) with ESMTP id 428D1650727 for ; Thu, 10 Jul 2008 23:56:50 -0300 (ADT) Received: by yw-out-2324.google.com with SMTP id 3so1657976ywj.73 for ; Thu, 10 Jul 2008 19:56:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=znwmax7UcRI4JrrbKH1O5p3OGIdnfUDSfo9itybcnAI=; b=GTXvM99+UjM7IvtB5d6fHvmjFhyQlfQ/Ybd2Wb8nnrxW+Vr0yNbBAGIUxWFpBRM+lQ gRhwGlvAKxQ9oI2ZqM7mlwp+/RG0TmMOscvp2wiSWIHXlIQn0eq4Nf/0jmeli3Q/hyV3 shhSfN4v4vmN7htAGb3nJ17FGQEYoPLZeHjqI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=IDT8jfx9LzyUAyOA8O/U0xf2hla3sxzjB2yoiMEWkdaniQDD8bLaHZPpSfe4Yk1YA2 /mz86KA2VwAeZd5sfT+isRC374dg9dvd5vBUf40XKM1uKPmmA0Hd9izi6OW5V2WmgR/U vPhQ3/9wKqi50OxxsTGvv8bnYL4HnW5k38ug8= Received: by 10.143.155.7 with SMTP id h7mr2880654wfo.16.1215745007202; Thu, 10 Jul 2008 19:56:47 -0700 (PDT) Received: by 10.142.222.13 with HTTP; Thu, 10 Jul 2008 19:56:47 -0700 (PDT) Message-ID: <57a815bf0807101956x1164e095j7433d8e1e1bc5b7e@mail.gmail.com> Date: Fri, 11 Jul 2008 12:56:47 +1000 From: "Mikel Lindsaar" To: pgsql-admin@postgresql.org Subject: Re: Importing data - possible UTF8 import bug? In-Reply-To: <57a815bf0807101902o193644ear50e211e67663d874@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <57a815bf0807101902o193644ear50e211e67663d874@mail.gmail.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200807/108 X-Sequence-Number: 29718 > Anyone got any ideas how I can hunt down what is in this row, visually > looking at it hasn't helped? As a followup, I am getting this same sort of error at various points on the file. So I tried taking the line, and cleaning it with Iconv and turning it into an ASCII sequence and inserting it back into the file. I still get the same error with the same invalid character.... too weird. I have a few lines that fail, all with different invalid character encodings: 0xe92042 0xe42050 0xa2 0xc220 0xdb20 0xe42050 0xe92042 It's at the rate of about one every 50,000 rows... so no real big deal... but still... -- http://lindsaar.net/ Rails, RSpec and Life blog....