Re: I dont get it, dump / restore failures to the same cluster.
| От | Tom Lane |
|---|---|
| Тема | Re: I dont get it, dump / restore failures to the same cluster. |
| Дата | |
| Msg-id | 1534.1148502512@sss.pgh.pa.us обсуждение исходный текст |
| Ответ на | I dont get it, dump / restore failures to the same cluster. (Michael Ben-Nes <miki@canaan.co.il>) |
| Ответы |
Re: I dont get it,
|
| Список | pgsql-general |
Michael Ben-Nes <miki@canaan.co.il> writes:
> pg_dump -Fc sourcedb > sourcedb-Fc.dump
> pg_dump -a sourcedb > sourcedb.dump
> createdb test
> pg_restore -c -s -d test sourcedb-Fc.dump
> psql test < sourcedb.dump
Is there a particularly good reason for doing it that way?
> I got few errors ( here are some of them ):
> ERROR: insert or update on table "logo_product" violates foreign key constraint "logo_product_product_id_fkey"
In general, separate schema and data restore doesn't work in the
presence of foreign keys. (This is probably impossible for pg_dump
to handle fully, because there could be circular FK dependencies;
so it doesn't even try ATM.) Do it the easy way and use a combined
schema-plus-data dump/restore. Or if you've just got to do it that
way, drop the FK constraints, load the data, re-add the constraints.
regards, tom lane
В списке pgsql-general по дате отправления: