From: | Alan Hodgson <ahodgson(at)simkin(dot)ca> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: pg_dump and pg_restore problem |
Date: | 2009-04-30 22:19:25 |
Message-ID: | 200904301519.25461@hal.medialogik.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wednesday 29 April 2009, "Michele Petrazzo - Unipex"
<michele(dot)petrazzo(at)unipex(dot)it> wrote:
> The unique solution that I found it's that to export with pg_dump all my
> tables except the table_three and, after, exporting only that and on the
> other host and import that alone...
>
> It's this a normal behavior, a "missing feature", or...?
pg_dump and pg_restore correctly backup and restore complete databases.
Partial backups and restores work, but of course can create expected
dependency problems that only the operator is in a position to resolve.
In your case you restored the complete schema and then tried to import data,
which failed due to a foreign key constraint. In a full backup and restore,
all the table data would have been restored prior to that constraint being
created.
--
Even a sixth-grader can figure out that you can’t borrow money to pay off
your debt
From | Date | Subject | |
---|---|---|---|
Next Message | Raymond O'Donnell | 2009-04-30 22:49:25 | Re: ERROR: syntax error at or near "IF"... why? |
Previous Message | Michael P. Soulier | 2009-04-30 20:15:02 | Re: how do you get there from here? |