X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id CC1B911F60B1 for ; Wed, 26 Apr 2006 12:01:49 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 29658-06-4 for ; Wed, 26 Apr 2006 12:01:28 -0300 (ADT) X-Greylist: delayed 18:43:39.520654 by SQLgrey- Received: from mail.liquidcore.com (mail.liquidcore.com [70.151.60.104]) by postgresql.org (Postfix) with ESMTP id CC5C411F633C for ; Wed, 26 Apr 2006 12:01:27 -0300 (ADT) Received: (from root@localhost) by mail.liquidcore.com (8.13.1/8.13.1) id k3QF1aKe017951; Wed, 26 Apr 2006 10:01:36 -0500 Received: from [192.168.0.81] (ppasalalinux.nqadmin.com [192.168.0.81]) by mail.liquidcore.com (8.13.1/8.13.1) with ESMTP id k3QF1aW3017865; Wed, 26 Apr 2006 10:01:36 -0500 Message-ID: <444F8B3E.8070706@nqadmin.com> Date: Wed, 26 Apr 2006 10:01:18 -0500 From: Prasanth Reply-To: dbadmin@nqadmin.com User-Agent: Thunderbird 1.5 (X11/20060313) MIME-Version: 1.0 To: John DeSoi CC: pgsql-admin@postgresql.org Subject: Re: Invalid UTF8 & Large Objects References: <444E83EA.7030808@nqadmin.com> <3CD2AC11-A33B-4847-AC9F-1BF74B6EBDCA@pgedit.com> In-Reply-To: <3CD2AC11-A33B-4847-AC9F-1BF74B6EBDCA@pgedit.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-scanner: Scanned for malicious content X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200604/278 X-Sequence-Number: 21447 I did the following and it worked. 1. Did a text pg_dump and used iconv to remove invalid characters and then loaded this into the database. 2. Took a dump created using -Fc and restored just the pg_largeobject table. Every thing seems to be good. I don't see the -b option in pg_dump in 8.1.3 so am I right in saying that large objects are automatically added to the dump? Thanks, -Prasanth. John DeSoi wrote: > > On Apr 25, 2006, at 4:17 PM, Prasanth wrote: > >> But then my problem is I have to do a text dump to use iconv in which >> case I will loose the large objects. >> I tried using the iconv on the dump generated using the -Fc option and >> then when I try to restore that I am getting the following error >> pg_restore: [archiver] entry ID 0 out of range -- perhaps a corrupt TOC > > -Fc produces a binary format, so you can't use iconv on it. One option > might be to write a script to export your large objects, dump text only > and fix with iconv, then reload the database and import the large objects. > > > > John DeSoi, Ph.D. > http://pgedit.com/ > Power Tools for PostgreSQL > > > ---------------------------(end of broadcast)--------------------------- > TIP 5: don't forget to increase your free space map settings