Re: Foreign Key ON DELETE CASCADE Performance
| От | Bruno Wolff III |
|---|---|
| Тема | Re: Foreign Key ON DELETE CASCADE Performance |
| Дата | |
| Msg-id | 20040430172436.GA14711@wolff.to обсуждение |
| Ответ на | Foreign Key ON DELETE CASCADE Performance (Chris Gamache <cgg007@yahoo.com>) |
| Ответы |
Re: Foreign Key ON DELETE CASCADE Performance
|
| Список | pgsql-general |
On Fri, Apr 30, 2004 at 09:35:39 -0700, Chris Gamache <cgg007@yahoo.com> 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.
В списке pgsql-general по дате отправления: