Re: Foreign key slows down copy/insert
От
Christopher Kings-Lynne
Тема
Re: Foreign key slows down copy/insert
Дата
Msg-id
425E8C0B.8060408@familyhealth.com.au
Ответ на
Re: Foreign key slows down copy/insert (Richard van den Berg)
Список
Дерево обсуждения
Foreign key slows down copy/insert Richard van den Berg <richard.vandenberg@trust-factory.com>
Re: Foreign key slows down copy/insert Christopher Kings-Lynne <chriskl@familyhealth.com.au>
Re: Foreign key slows down copy/insert Richard van den Berg <richard.vandenberg@trust-factory.com>
Re: Foreign key slows down copy/insert Stephan Szabo <sszabo@megazone.bigpanda.com>
Re: Foreign key slows down copy/insert Tom Lane <tgl@sss.pgh.pa.us>
Re: Foreign key slows down copy/insert Stephan Szabo <sszabo@megazone.bigpanda.com>
Re: Foreign key slows down copy/insert Christopher Kings-Lynne <chriskl@familyhealth.com.au>
Re: Foreign key slows down copy/insert Richard van den Berg <richard.vandenberg@trust-factory.com>
Re: Foreign key slows down copy/insert Christopher Kings-Lynne <chriskl@familyhealth.com.au>
Re: Foreign key slows down copy/insert Tom Lane <tgl@sss.pgh.pa.us>
Re: Foreign key slows down copy/insert Richard van den Berg <richard.vandenberg@trust-factory.com>
Re: Foreign key slows down copy/insert Christopher Kings-Lynne <chriskl@familyhealth.com.au>
Re: Foreign key slows down copy/insert Marko Ristola <marko.ristola@kolumbus.fi>
Re: Foreign key slows down copy/insert PFC <lists@boutiquenumerique.com>
Re: Foreign key slows down copy/insert Richard van den Berg <richard.vandenberg@trust-factory.com>
Re: Foreign key slows down copy/insert PFC <lists@boutiquenumerique.com>
Re: Foreign key slows down copy/insert Richard van den Berg <richard.vandenberg@trust-factory.com>
Re: Foreign key slows down copy/insert Christopher Kings-Lynne <chriskl@familyhealth.com.au>
Re: Foreign key slows down copy/insert Richard van den Berg <richard.vandenberg@trust-factory.com>
Re: Foreign key slows down copy/insert Tom Lane <tgl@sss.pgh.pa.us>
Re: Foreign key slows down copy/insert Richard van den Berg <richard.vandenberg@trust-factory.com>
> 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. Just drop the fk and re-add it, until postgres gets more smarts. Chris
В списке pgsql-performance по дате отправления