From: Ivan Voras <ivoras@fer.hr>
To: pgsql-performance@postgresql.org
Subject: Optimizing DELETE
Date: Tue, 19 Sep 2006 15:22:34 +0200
Message-ID: <450FEF1A.4070106@fer.hr> (raw)
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)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: ivoras@fer.hr
Subject: Re: Optimizing DELETE
In-Reply-To: <450FEF1A.4070106@fer.hr>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox