Re: Foreign Key ON DELETE CASCADE Performance - Mailing list pgsql-general

From Bruno Wolff III
Subject Re: Foreign Key ON DELETE CASCADE Performance
Date
Msg-id 20040430172436.GA14711@wolff.to
Whole thread Raw
In response to Foreign Key ON DELETE CASCADE Performance  (Chris Gamache <cgg007@yahoo.com>)
Responses Re: Foreign Key ON DELETE CASCADE Performance
List 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 by date:

Previous
From: Ian Ribas
Date:
Subject: Re: Optimizer choosing smaller index instead of right one
Next
From: Paul Thomas
Date:
Subject: Re: JDBC caching plpgsql function errors?