Re: Foreign Key ON DELETE CASCADE Performance

From: Bruno Wolff III <bruno(at)wolff(dot)to>
To: Chris Gamache <cgg007(at)yahoo(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Foreign Key ON DELETE CASCADE Performance
Date: 2004-04-30 17:24:36
Message-ID: 20040430172436.GA14711@wolff.to
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, Apr 30, 2004 at 09:35:39 -0700,
Chris Gamache <cgg007(at)yahoo(dot)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.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Paul Thomas 2004-04-30 18:00:58 Re: JDBC caching plpgsql function errors?
Previous Message CS Wagner 2004-04-30 17:17:16 Load Balancing and Backup