From: Jesper Krogh <jesper@krogh.cc>
To: pgsql-admin@postgresql.org
Subject: Upgrade time, dump+restore trouble.
Date: Wed, 17 Oct 2007 16:18:21 +0200
Message-ID: <471619AD.9020903@krogh.cc> (raw)
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: jesper@krogh.cc
Subject: Re: Upgrade time, dump+restore trouble.
In-Reply-To: <471619AD.9020903@krogh.cc>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox