Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id B8E5F9FB1C4 for ; Tue, 28 Nov 2006 11:47:11 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-new, port 10024) with ESMTP id 42708-04 for ; Tue, 28 Nov 2006 11:46:58 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 365889FB1DF for ; Tue, 28 Nov 2006 11:46:59 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id kASFkuH7006114; Tue, 28 Nov 2006 10:46:56 -0500 (EST) To: Peter Wilson cc: pgsql-admin@postgresql.org Subject: Re: Problem restoring with pg_dump In-reply-to: References: Comments: In-reply-to Peter Wilson message dated "Tue, 28 Nov 2006 10:00:37 +0000" Date: Tue, 28 Nov 2006 10:46:56 -0500 Message-ID: <6113.1164728816@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200611/227 X-Sequence-Number: 23754 Peter Wilson writes: > pg_restore : [custom archiver] Dumping a specific TOC data block out of order is > not supported without ID on this input stream (fseek required). Could you show us the unmodified output from pg_restore -l, as well as the edits you made to produce the -L script? regards, tom lane