Re: DELETE eats up all memory and crashes box

From: "Worky Workerson" <worky(dot)workerson(at)gmail(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: DELETE eats up all memory and crashes box
Date: 2006-10-06 19:23:16
Message-ID: ce4072df0610061223q16a76ae7sd394762f9ef6ada4@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> Note that whether you have CASCADE or not is not the issue --- if you
> are doing a delete in a foreign-key-referenced relation at all, you
> are going to have a trigger event per deleted row no matter what the
> details of the FK are.

So the best/fastest* way to do this would be to remove the FK
relationship from the tables, delete all my rows with DELETE ... WHERE
ip IN (SELECT ...) in the previously FK-ed tables, delete all the
rows in the PK table, then recreate the FK relationships? I tried
this and it was pretty snappy, assuming that all the indexes are
built.

*note: loading/creating a datawarehouse, guaranteed exclusive access.
Current DW size is about 10 GB.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Marc Munro 2006-10-06 20:15:59 Alter table alter column
Previous Message Chris Hoover 2006-10-06 19:22:48 how to get number of minutes?