Re: fine tuned database dump/reload?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Douglas McNaught <doug(at)mcnaught(dot)org>
Cc: Dan Armbrust <daniel(dot)armbrust(dot)list(at)gmail(dot)com>, "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: fine tuned database dump/reload?
Date: 2005-10-17 16:36:14
Message-ID: 9502.1129566974@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Douglas McNaught <doug(at)mcnaught(dot)org> writes:
> Dan Armbrust <daniel(dot)armbrust(dot)list(at)gmail(dot)com> writes:
>> Maybe I missed something then, because it didn't last time I tried to
>> move some data. I had to drop my foreign keys before I could reload
>> it.

> What version was this? Older versions definitely had some problems
> with table ordering. In 8.0.X, the tables in the dump all get loaded
> before the FK constraints are created, and I have never seen a
> problem.

Even in current versions, you have to do a full (schema+data) dump for
it to work "right". Data-only dumps are prone to FK problems. This
is insoluble in the general case, though you can work around it to some
extent with the --disable-triggers option.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Nikolay Samokhvalov 2005-10-17 16:38:19 Re: Setting up a fine-grained permission system
Previous Message Dean Gibson (DB Administrator) 2005-10-17 16:35:34 Planner regression in 8.0.x ?