pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
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 19:01:33 -0400
Message-ID: <12597.1192662093@sss.pgh.pa.us> (raw)
In-Reply-To: <47165E55.4020807@krogh.cc>
References: <471619AD.9020903@krogh.cc>
	<7031.1192637434@sss.pgh.pa.us>
	<47165E55.4020807@krogh.cc>

Jesper Krogh <jesper@krogh.cc> writes:
> Tom Lane wrote:
>> Drop the constraints in the source database.

> That would be my workaround for the problem. But isn't it somehow
> desirable that pg_dumpall | psql "allways" would work?

Well, sure.  The reason why this sort of thing is deprecated is exactly
that the database can't promise it will work all the time.  The DB has
no way to know that your constraints do something they're not supposed
to, and in particular no way to infer that there's a specific data
loading order needed to keep the constraint from failing.

We do allow you to do it, but if it breaks you get to keep both pieces.

			regards, tom lane



view thread (5+ messages)  latest in thread

Message-ID: <12597.1192662093@sss.pgh.pa.us>
Permalink:  ../12597.1192662093@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/12597.1192662093@sss.pgh.pa.us

 · 

reply

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: <12597.1192662093@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