From: | Daniel Åkerud <zilch(at)home(dot)se> |
---|---|
To: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Foreign Keys Constraints, perforamance analysis |
Date: | 2001-06-25 09:32:26 |
Message-ID: | 009001c0fd59$bf22f5f0$c901a8c0@automatic100 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
OK, I've been discussing this with a collegue of mine... and I'm starting to
see the light here...
I will, first of all, make a new, simpler, 1<->1 realtionship to test FK
constraints... no 2<->1<->2 relasionship here...
Person -> Item/item_fkc
And I will do no bulk-delete. Instead these tests:
Fill person. no time measuring.
Fill item, no foreign keys constraints, time measuring.
Fill item, foreign keys constraints
Compare last to measurments. How much do you loose in performance having the
Foreign Key check?
For all persons {
if (fkc)
delete from person where id = $id
else
delete from person where id = $id; delete from item where personid=$id
}
Compare measurements. How much do you loose having the foreign keys
constraints delete the item?
This, I think, this is a more fair comparison.
Can you call the FK itself a foreign key constraint, as it actually is
constraining something?
Thanks Stephan and Tom for the help! Greatly appreciated!!
From | Date | Subject | |
---|---|---|---|
Next Message | Jan Wieck | 2001-06-25 12:47:50 | Re: Foreign Keys Constraints, perforamance analysis |
Previous Message | Eliel Mamousette | 2001-06-25 08:53:53 | RE: to_timestamp busted? |