Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 6A5FF9FB326 for ; Wed, 17 Oct 2007 11:37:31 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 07148-01 for ; Wed, 17 Oct 2007 11:36:56 -0300 (ADT) X-Greylist: delayed 00:18:36.118579 by SQLgrey-1.7.5 Received: from shrek.krogh.cc (2605ds1-ynoe.1.fullrate.dk [90.184.12.24]) by postgresql.org (Postfix) with ESMTP id 2E7249FB295 for ; Wed, 17 Oct 2007 11:37:09 -0300 (ADT) Received: from localhost (localhost.localdomain [127.0.0.1]) by shrek.krogh.cc (Postfix) with ESMTP id A0CCA197344 for ; Wed, 17 Oct 2007 16:18:32 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at shrek.krogh.cc Received: from shrek.krogh.cc ([127.0.0.1]) by localhost (shrek.krogh.cc [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Rx+gzxXLQfxj for ; Wed, 17 Oct 2007 16:18:24 +0200 (CEST) Received: from [90.184.13.233] (unknown [90.184.13.233]) by shrek.krogh.cc (Postfix) with ESMTP id E40863BF29A for ; Wed, 17 Oct 2007 16:18:23 +0200 (CEST) Message-ID: <471619AD.9020903@krogh.cc> Date: Wed, 17 Oct 2007 16:18:21 +0200 From: Jesper Krogh User-Agent: Thunderbird 1.5.0.13 (X11/20070824) MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: Upgrade time, dump+restore trouble. X-Enigmail-Version: 0.94.2.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200710/155 X-Sequence-Number: 27069 We have a quite large (in our measurements) database, currently around 150GB of data. Time has come to upgrade to 8.2.5 from 8.1.10. Going to the fine manual.. having a system where both databases are installed PG8.1 on port 5432 and PG8.2 on port 5433, logging in as the "postgres" user and running: pg_dumpall | psql -p 5433 This fails due to constraints on the tables. Typical error messages look like: ERROR: new row for relation "box_full" violates check constraint "tower_id_ref" The tables are running a "home-made" timetravelling feature where a contraint on the table implements the foreing keys on the table. How can I instruct pg_dumpall to turn off these constriants during dump/restore? Jesper -- Jesper Krogh, jesper@krogh.cc