X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 63721DB6F2 for ; Tue, 1 Nov 2005 14:47:11 -0400 (AST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 48362-09 for ; Tue, 1 Nov 2005 18:47:08 +0000 (GMT) Received: from mail24.sea5.speakeasy.net (mail24.sea5.speakeasy.net [69.17.117.26]) by svr1.postgresql.org (Postfix) with ESMTP id 03D0CDB6F0 for ; Tue, 1 Nov 2005 14:47:08 -0400 (AST) Received: (qmail 29298 invoked from network); 1 Nov 2005 18:47:08 -0000 Received: from mail.kinesis-cem.com (HELO pdarley) (kinesis@[64.81.9.230]) (envelope-sender ) by mail24.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 1 Nov 2005 18:47:08 -0000 From: "Peter Darley" To: "Pgsql-Admin" Subject: Can't dump and restore Date: Tue, 1 Nov 2005 10:52:20 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506 Importance: Normal X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0 required=5 tests=[none] X-Spam-Score: 0 X-Spam-Level: X-Archive-Number: 200511/10 X-Sequence-Number: 19383 Folks, I'm having some trouble restoring data that was dumped from my database. When I dump out a table (pg_dump -d neo -t question > question.tbl) and try to restore it (psql -d temp -f question.tbl) I get errors on certain rows: "psql:question.tbl:15861: ERROR: invalid byte sequence for encoding "UNICODE": 0xe96520". This happens when I use SQL_ASCII or UNICODE as the encoding. I didn't try any other encodings. When I do this with a table, it's missing the rows that throw the error. When I do it with a full database dump, the tables that have rows that throw the errors are empty (I assume it's just cancleing the transaction). What is confounding me is that this is data that is currently in the database, unless the dump is creating errors as it goes, which doesn't seem likely. It is always the same rows as well. Why would it be rejecting data that it obvously accepted once? The computer is running FC4 64 SMP. The version() of PostgreSQL is: "Linux version 2.6.13-1.1526_FC4smp (bhcompile@hs20-bc1-1.build.redhat.com) (gcc version 4.0.1 20050727 (Red Hat 4.0.1-5)) #1 SMP Wed Sep 28 19:28:24 EDT 2005" Does anyone have any idea of what might be going on here? Is this likely to be something that I can fix, or should I start taring up the directory when I need to do backups? Thanks, Peter Darley