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 59DB8D1D614 for ; Thu, 22 Apr 2004 03:45:31 -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 08006-04 for ; Thu, 22 Apr 2004 03:45:30 -0300 (ADT) Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by svr1.postgresql.org (Postfix) with ESMTP id 11BD3D1D2B5 for ; Thu, 22 Apr 2004 03:45:28 -0300 (ADT) Received: from cjwhitew2k02 (sjc-vpn1-976.cisco.com [10.21.99.208]) by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id i3M6jF0Q006991; Wed, 21 Apr 2004 23:45:16 -0700 (PDT) Reply-To: From: "Chris White (cjwhite)" To: "'Tom Lane'" Cc: Subject: Re: Problems doing a restore under 7.4.2 Date: Wed, 21 Apr 2004 23:45:27 -0700 Message-ID: <00aa01c42835$660f6840$0300a8c0@amer.cisco.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4024 In-Reply-To: <19432.1082606525@sss.pgh.pa.us> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Virus-Scanned: by amavisd-new at postgresql.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200404/285 X-Sequence-Number: 13258 I got around the problem by using the --disable-triggers option on the restore. Chris -----Original Message----- From: Tom Lane [mailto:tgl@sss.pgh.pa.us] Sent: Wednesday, April 21, 2004 9:02 PM To: cjwhite@cisco.com Cc: pgsql-admin@postgresql.org Subject: Re: [ADMIN] Problems doing a restore under 7.4.2 "Chris White (cjwhite)" writes: > I have done a backup of my 7.4.2 database using pg_dump. When I > restore the database using the -c option I get the following error > message and pg_restore fails > pg_restore: [archiver (db)] could not execute query: ERROR: trigger > "RI_ConstraintTrigger_17371" for table "vm_message" does not exist Probably an ordering issue --- easiest workaround is not to use -c, I'd think. If you like, you could try CVS-tip pg_dump to see if it gets the ordering right. regards, tom lane