Re: Foreign Key ON DELETE CASCADE Performance
От
Chris Gamache
Тема
Re: Foreign Key ON DELETE CASCADE Performance
Дата
Msg-id
20040430193620.62742.qmail@web13806.mail.yahoo.com
Ответ на
Re: Foreign Key ON DELETE CASCADE Performance (Bruno Wolff III)
Список
Дерево обсуждения
Plpgsql problem passing ROWTYPE to function "Karl O. Pinc" <kop@meme.com>
Re: Plpgsql problem passing ROWTYPE to function Tom Lane <tgl@sss.pgh.pa.us>
Re: Plpgsql problem passing ROWTYPE to function "Karl O. Pinc" <kop@meme.com>
Re: Plpgsql problem passing ROWTYPE to function Tom Lane <tgl@sss.pgh.pa.us>
Re: Plpgsql problem passing ROWTYPE to function "Karl O. Pinc" <kop@meme.com>
Foreign Key ON DELETE CASCADE Performance Chris Gamache <cgg007@yahoo.com>
Re: Foreign Key ON DELETE CASCADE Performance Bruno Wolff III <bruno@wolff.to>
Re: Foreign Key ON DELETE CASCADE Performance Chris Gamache <cgg007@yahoo.com>
Bruno, you're a genius! :) I /had/ missed adding a single index. It made all the difference in the world. Boy! That's a relief. CG --- Bruno Wolff III wrote: > On Fri, Apr 30, 2004 at 09:35:39 -0700, > Chris Gamache wrote: > > > > What can be done to increase the overall speed of this transaction, keeping > the > > FKey Constraints in-place? > > The fastest thing to do if you really want to get rid of everything is > do delete from for each of the tables starting with the ones that don't > have any tables dependent on them. > > Another thing to note is that postgres doesn't automatically create > an index on columns that reference another table. When you are taking > advantage of cascading deletes you normally will want an index on such > columns. If you insist upon being able to do the delete using just a delete > from table1 you will want to create these indexes. __________________________________ Do you Yahoo!? Win a $20,000 Career Makeover at Yahoo! HotJobs http://hotjobs.sweepstakes.yahoo.com/careermakeover
В списке pgsql-general по дате отправления