X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 0C9F7D1B47D; Wed, 21 Apr 2004 13:05:51 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 23761-03; Wed, 21 Apr 2004 13:05:47 -0300 (ADT) Received: from psplotp1.transplace.com (mail.transplace.com [65.64.216.31]) by svr1.postgresql.org (Postfix) with ESMTP id BA804D1B482; Wed, 21 Apr 2004 13:05:46 -0300 (ADT) Subject: Re: problem with pg_dump and pg_restore To: Grega Bremec Cc: pgsql-admin@postgresql.org, pgsql-admin-owner@postgresql.org, Fischer Ulrich X-Mailer: Lotus Notes Release 5.0.8 June 18, 2001 Message-ID: From: Corey.Brune@transplace.com Date: Wed, 21 Apr 2004 11:05:42 -0500 X-MIMETrack: Serialize by Router on psplotp1/com(Release 5.0.11 |July 24, 2002) at 04/21/2004 11:05:46 AM MIME-Version: 1.0 Content-type: multipart/mixed; Boundary="0__=09BBE4EEDFCB9F0D8f9e8a93df938690918c09BBE4EEDFCB9F0D" Content-Disposition: inline X-Virus-Scanned: by amavisd-new at postgresql.org X-Spam-Status: No, hits=0.3 tagged_above=0.0 required=5.0 tests=NO_REAL_NAME X-Spam-Level: X-Archive-Number: 200404/278 X-Sequence-Number: 13251 --0__=09BBE4EEDFCB9F0D8f9e8a93df938690918c09BBE4EEDFCB9F0D Content-type: text/plain; charset=us-ascii When I tried to use the 7.3.2 dump, and use 7.4.1 import, I had several issues- mostly with data. I actually had to dump with the 7.4.1 dumpall command, upgrade the DB to 7.4.1, and then everything imported correctly. Hope this helps, Corey Grega Bremec um.si> cc: pgsql-admin@postgresql.org Sent by: Subject: Re: [ADMIN] problem with pg_dump and pg_restore pgsql-admin-owner@pos tgresql.org 04/21/2004 08:28 AM ...and on Wed, Apr 21, 2004 at 02:46:54PM +0200, Fischer Ulrich used the keyboard: > Hi > > I try to move my datas from a postresql 7.3.2 to a postgresql 7.4.1. The > database was dumped with: > > pg_dumpall -g GLOBALobjects.sql > pg_dump -s DATABASE > DBschema.sql > pg_dump -Fc DATABASE > DBdata.tar > Why the schema/data separation? One important freedom you get when combining schema and data in the dumps is you can alter it after you imported the data and thus avoid cyclic dependencies where existance of one foreign key mandates the existance of another, which refers to the first one. For now though, try eliminating all constraints from the schema dump and ALTERing the tables after you imported the data. Hope this helped, -- Grega Bremec Senior Administrator Noviforum Ltd., Software & Media http://www.noviforum.si/ (See attached file: att4aa3m.dat) --0__=09BBE4EEDFCB9F0D8f9e8a93df938690918c09BBE4EEDFCB9F0D Content-type: application/octet-stream; name="att4aa3m.dat" Content-Disposition: attachment; filename="att4aa3m.dat" Content-transfer-encoding: base64 LS0tLS1CRUdJTiBQR1AgU0lHTkFUVVJFLS0tLS0NClZlcnNpb246IEdudVBH IHYxLjIuMyAoR05VL0xpbnV4KQ0KDQppRDhEQlFGQWhuYjNEby9FTVlENCtv c1JBbS9HQUtDWC90dUNYWmNWVmszcG02RTJWT29JcjlweWh3Q2dqbDllDQow N2UvdGpKRzR4blVpR1Y3aElpSWVGZz0NCj1hbXZkDQotLS0tLUVORCBQR1Ag U0lHTkFUVVJFLS0tLS0NCg== --0__=09BBE4EEDFCB9F0D8f9e8a93df938690918c09BBE4EEDFCB9F0D--