Jesper Krogh <jesper@xxxxxxxx> 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
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
