From: | Markus Mehrwald <mehrwald(at)ira(dot)uka(dot)de> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: problem with foreign keys + data-only backup |
Date: | 2008-08-22 13:48:43 |
Message-ID: | 48AEC3BB.7080107@ira.uka.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi,
I do not think this will work. As far as I know foreign key checks are
not triggers. Postgres is very strict with things concerning referential
integrity so you cannot turn them off.
Maybe it will help to use "--orig-order" for creating the dump.
Markus
Richard Huxton schrieb:
> Peter Billen wrote:
>> Hi all,
>>
>> I have a problem with foreign keys and data-only (no schema) backup. I
>> have a simple table node (pseudo-SQL):
>
>> When I do a data-only backup, the backup file contains following two lines:
>>
>> INSERT INTO NODE (node_id, parent_node_id) VALUES (2, 1);
>> INSERT INTO NODE (node_id, parent_node_id) VALUES (1, NULL);
>>
>> Restoring the backup file into another database ofcourse fails, because
>> the parent_node_id (1) in the first INSERT statement refers to an
>> unknown (to be added) node (in the second statement).
>>
>> How do I make sure my backup orders the insert statements in a logical
>> order?
>
> You don't. You might find --disable-triggers useful though. See the
> pg_restore documentation for details.
>
--
Dipl.-Inform. Med. Markus Mehrwald
Institut für Prozessrechentechnik, Automation und Robotik
Medizin-Gruppe
Universität Karlsruhe (TH)
Gebäude 40.28, Zimmer 110
Engler-Bunte-Ring 8
76131 Karlsruhe
Fon: +49 (721) 608-7113
Fax: +49 (721) 608-7141
From | Date | Subject | |
---|---|---|---|
Next Message | Sam Mason | 2008-08-22 14:38:02 | Re: SERIAL datatype |
Previous Message | Richard Huxton | 2008-08-22 13:28:43 | Re: problem with foreign keys + data-only backup |