Received: from localhost (unknown [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 4F6A39FBC2A for ; Wed, 17 Oct 2007 13:10:43 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-maia, port 10024) with ESMTP id 25814-02-2 for ; Wed, 17 Oct 2007 13:10:38 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 481D89FBC8A for ; Wed, 17 Oct 2007 13:10:38 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.1/8.14.1) with ESMTP id l9HGAYV1007032; Wed, 17 Oct 2007 12:10:34 -0400 (EDT) To: Jesper Krogh cc: pgsql-admin@postgresql.org Subject: Re: Upgrade time, dump+restore trouble. In-reply-to: <471619AD.9020903@krogh.cc> References: <471619AD.9020903@krogh.cc> Comments: In-reply-to Jesper Krogh message dated "Wed, 17 Oct 2007 16:18:21 +0200" Date: Wed, 17 Oct 2007 12:10:34 -0400 Message-ID: <7031.1192637434@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200710/156 X-Sequence-Number: 27070 Jesper Krogh writes: > The tables are running a "home-made" timetravelling feature where a > contraint on the table implements the foreing keys on the table. You mean you have check constraints that do selects on other tables? You have just found out (one reason) why that's a bad idea. > How can I instruct pg_dumpall to turn off these constriants during > dump/restore? Drop the constraints in the source database. regards, tom lane