Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 146079FA8EF for ; Tue, 28 Nov 2006 09:29:52 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-new, port 10024) with ESMTP id 06215-01 for ; Tue, 28 Nov 2006 09:29:46 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from ns1.peker.com.pl (181-ego-2.acn.waw.pl [62.121.85.181]) by postgresql.org (Postfix) with SMTP id 7AA659FA231 for ; Tue, 28 Nov 2006 09:29:45 -0400 (AST) Received: (qmail 5958 invoked by uid 540); 28 Nov 2006 13:19:57 -0000 Received: from 153.19.179.26 by ns1.peker.com.pl (envelope-from , uid 401) with qmail-scanner-1.25st (clamdscan: 0.82/760. spamassassin: 3.0.2. perlscan: 1.25st. Clear:RC:1(153.19.179.26):. Processed in 0.080046 secs); 28 Nov 2006 13:19:57 -0000 Received: from rzgw.artnet.pl (HELO ?10.4.128.107?) (informatyka-adamr@153.19.179.26) by ns1.peker.com.pl with SMTP; 28 Nov 2006 13:19:57 -0000 Message-ID: <456C390B.6030209@informatyka.gdansk.pl> Date: Tue, 28 Nov 2006 14:26:35 +0100 From: Adam Radlowski User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050716) X-Accept-Language: pl, en-us, en MIME-Version: 1.0 To: Peter Wilson CC: pgsql-admin@postgresql.org Subject: Re: Problem restoring with pg_dump References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200611/226 X-Sequence-Number: 23753 I had problems, like that. I've omitted them using "plain" format (SQL script file) of dump file. I restore data from "plain" format with psql - using command "\i FILE". It work always. If You gzip this "plain" file - You become simillar volume of file using binary dump format. Greetings Adam Peter Wilson wrote: >I posted this to 'general' yesterday but with no luck. This is probably a better >group. > >I've just got the following message while trying to restore a database : > >pg_restore : [custom archiver] Dumping a specific TOC data block out of order is >not supported without ID on this input stream (fseek required). > >The command was : >pg_restore -L /tmp/toc --dbname=whitebeam --disable-triggers --username=postgres >/var/backups/restore-db.psql > >/tmp/toc is a re-orderd output from : > >pg_restore -l -a /var/backups/restore-db.psql > /tmp/toc > >Using Postgres 8.1.4 on >Linux version 2.6.15-1.2054_FC5 > >The dump itself was made on another machine running 8.1.4 on Fedora core 4. > >I've run similar commands on this machine before with no problems. Not sure why >I should start to have these problems now? > >Anyone else seen anything similar? Thoughts much appreciated! > >Pete > >---------------------------(end of broadcast)--------------------------- >TIP 1: if posting/reading through Usenet, please send an appropriate > subscribe-nomail command to majordomo@postgresql.org so that your > message can get through to the mailing list cleanly > > > >