From: | Philip Warner <pjw(at)rhyme(dot)com(dot)au> |
---|---|
To: | "Stephan Szabo" <sszabo(at)kick(dot)com> |
Cc: | <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: AW: Proposal: More flexible backup/restore via pg_dump |
Date: | 2000-06-29 10:33:03 |
Message-ID: | 3.0.5.32.20000629203303.03100c70@mail.rhyme.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
At 12:06 28/06/00 -0700, Stephan Szabo wrote:
>
>This will happen for check constraints, but not for foreign key
>constraints...
>It actually adds the fk constraints later with CREATE CONSTRAINT TRIGGER
>after the data dump is finished. And, if you do separate schema and data
>dumps, the wierd statements at the top and bottom of the data dump turn
>off triggers and then turn them on again (in the most painful way possible).
Thanks for this information!
I had not seen those statements before; I have been mistakenly modifying
6.5.3 sources, not 7.0.2. I will incorporate them in my work. Is there any
way of also disabling all constraint checking while loading the data?
----------------------------------------------------------------
Philip Warner | __---_____
Albatross Consulting Pty. Ltd. |----/ - \
(A.C.N. 008 659 498) | /(@) ______---_
Tel: (+61) 0500 83 82 81 | _________ \
Fax: (+61) 0500 83 82 82 | ___________ |
Http://www.rhyme.com.au | / \|
| --________--
PGP key available upon request, | /
and from pgp5.ai.mit.edu:11371 |/
From | Date | Subject | |
---|---|---|---|
Next Message | Zeugswetter Andreas SB | 2000-06-29 10:33:39 | AW: AW: Big 7.1 open items |
Previous Message | Zeugswetter Andreas SB | 2000-06-29 10:13:21 | AW: AW: Big 7.1 open items |