Received: from anchor-post-30.mail.demon.net (anchor-post-30.mail.demon.net [194.217.242.88]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f6AH3Va96592 for ; Tue, 10 Jul 2001 13:03:31 -0400 (EDT) (envelope-from dev@archonet.com) Received: from mwynhau.demon.co.uk ([193.237.186.96] helo=mainbox.archonet.com) by anchor-post-30.mail.demon.net with esmtp (Exim 2.12 #1) id 15K0v3-0004ST-0U; Tue, 10 Jul 2001 18:03:30 +0100 Received: from client (client.archonet.com [192.168.1.16]) by mainbox.archonet.com (Postfix) with SMTP id 528D01280D; Tue, 10 Jul 2001 17:47:36 +0100 (BST) Message-ID: <00a701c10960$05035760$1001a8c0@archonet.com> From: "Richard Huxton" To: "Josh Berkus" , References: Subject: Re: Problems with PG_DUMP and restore Date: Tue, 10 Jul 2001 17:47:31 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Archive-Number: 200107/109 X-Sequence-Number: 3894 From: "Josh Berkus" > Folks, > > In an effort to do some general cleanup in my database functions, I > dumped the schema (pgdump -s) and the data (pgdump -a) to seperate text > files. > > I editied and restored the schema fine. However, when I attemped to > restore the data (via \i filename), it failed selectively; some tables > were restored but many were not. No errors were logged. Try having a look at the order the tables get inserted esp. with regard to any foreign keys etc. - I'm not sure pgdump is that clever about such things. - Richard Huxton