Skip site navigation (1) Skip section navigation (2)

Re: Upgrade time, dump+restore trouble.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jesper Krogh <jesper(at)krogh(dot)cc>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: Upgrade time, dump+restore trouble.
Date: 2007-10-17 23:01:33
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-admin
Jesper Krogh <jesper(at)krogh(dot)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

In response to


pgsql-admin by date

Next:From: Kostis MentzelosDate: 2007-10-18 05:23:35
Subject: convert char to varchar
Previous:From: Alvaro HerreraDate: 2007-10-17 21:56:53
Subject: Re: postgresql para windows para 64 bits

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group