Received: from localhost (maia-3.hub.org [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 000FE9FB1CD for ; Tue, 28 Nov 2006 06:05:15 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-new, port 10024) with ESMTP id 77577-10 for ; Tue, 28 Nov 2006 06:05:11 -0400 (AST) Received: from news.hub.org (news.hub.org [200.46.204.72]) by postgresql.org (Postfix) with ESMTP id 9BAD59FA2CA for ; Tue, 28 Nov 2006 06:05:15 -0400 (AST) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.13.8/8.13.8) with ESMTP id kASA5EM7062611 for ; Tue, 28 Nov 2006 06:05:14 -0400 (AST) (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.13.8/8.13.8/Submit) id kASA0ewp061818 for pgsql-admin@postgresql.org; Tue, 28 Nov 2006 06:00:40 -0400 (AST) (envelope-from news) From: Peter Wilson X-Newsgroups: pgsql.admin Subject: Problem restoring with pg_dump Date: Tue, 28 Nov 2006 10:00:37 +0000 Organization: Hub.Org Networking Services Lines: 27 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@news.hub.org User-Agent: Thunderbird 1.5.0.8 (Windows/20061025) X-Enigmail-Version: 0.94.0.0 X-Antivirus: avast! (VPS 0651-0, 27/11/2006), Outbound message X-Antivirus-Status: Clean To: pgsql-admin@postgresql.org X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200611/223 X-Sequence-Number: 23750 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