Optimizing DELETE

From: Ivan Voras <ivoras(at)fer(dot)hr>
To: pgsql-performance(at)postgresql(dot)org
Subject: Optimizing DELETE
Date: 2006-09-19 13:22:34
Message-ID: 450FEF1A.4070106@fer.hr
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

I've just fired off a "DELETE FROM table" command (i.e. unfiltered
DELETE) on a trivially small table but with many foreign key references
(on similar-sized tables), and I'm waiting for it to finish. It's been
10 minutes now, which seems very excessive for a table of 9000 rows on a
3 GHz desktop machine.

'top' says it's all spent in USER time, and there's a ~~500KB/s write
rate going on. Just before this DELETE, I've deleted data from a larger
table (50000 rows) using the same method and it finished in couple of
seconds - maybe it's a PostgreSQL bug?

My question is: assuming it's not a bug, how to optimize DELETEs?
Increasing work_mem maybe?

(I'm using PostgreSQL 8.1.4 on FreeBSD 6- amd64)

(I know about TRUNCATE; I need those foreign key references to cascade)

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Rod Taylor 2006-09-19 13:53:07 Re: Optimizing DELETE
Previous Message Markus Schaber 2006-09-19 13:09:50 Re: High CPU Load