From: Richard van den Berg <richard.vandenberg@trust-factory.com>
To: Christopher Kings-Lynne <chriskl@familyhealth.com.au>
Cc: pgsql-performance@postgresql.org
Subject: Re: Foreign key slows down copy/insert
Date: Thu, 14 Apr 2005 17:25:36 +0200
Message-ID: <425E8B70.2060006@trust-factory.com> (raw)
In-Reply-To: <425E88B7.6000203@familyhealth.com.au>
References: <425E6045.4060201@trust-factory.com>
<425E792B.4020500@familyhealth.com.au>
<425E7D96.6020201@trust-factory.com>
<425E7F94.4080602@familyhealth.com.au>
<425E8766.8070901@trust-factory.com>
<425E88B7.6000203@familyhealth.com.au>
Christopher Kings-Lynne wrote:
> No it certainly won't warn you. You have _avoided_ the check entirely.
> That's why I was warning you...
I figured as much when I realized it was just a simple table update. I
was thinking more of a DB2 style "set integrity" command.
> If you wanted to be really careful, you could:
So I will be re-checking my own FKs. That's not really what I'd expect
from a FK.
My problem with this really is that in my database it is hard to predict
which inserts will be huge (and thus need FKs dissabled), so I would
have to code it around all inserts. Instead I can code my own integirty
logic and avoid using FKs all together.
Thanks,
--
Richard van den Berg, CISSP
-------------------------------------------
Trust Factory B.V. | www.dna-portal.net
Bazarstraat 44a | www.trust-factory.com
2518AK The Hague | Phone: +31 70 3620684
The Netherlands | Fax : +31 70 3603009
-------------------------------------------
Have you visited our new DNA Portal?
-------------------------------------------
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: richard.vandenberg@trust-factory.com, chriskl@familyhealth.com.au
Subject: Re: Foreign key slows down copy/insert
In-Reply-To: <425E8B70.2060006@trust-factory.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox