From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jesper Krogh <jesper@krogh.cc>
Cc: pgsql-admin@postgresql.org
Subject: Re: Upgrade time, dump+restore trouble.
Date: Wed, 17 Oct 2007 12:10:34 -0400
Message-ID: <7031.1192637434@sss.pgh.pa.us> (raw)
In-Reply-To: <471619AD.9020903@krogh.cc>
References: <471619AD.9020903@krogh.cc>
Jesper Krogh <jesper@krogh.cc> 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
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: tgl@sss.pgh.pa.us, jesper@krogh.cc
Subject: Re: Upgrade time, dump+restore trouble.
In-Reply-To: <7031.1192637434@sss.pgh.pa.us>
* 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