From: Jessica Richard <rjessil@yahoo.com>
To: pgsql-performance@postgresql.org
Subject: slow delete
Date: Thu, 3 Jul 2008 17:44:40 -0700 (PDT)
Message-ID: <357892.18257.qm@web56412.mail.re3.yahoo.com> (raw)
I have a table with 29K rows total and I need to delete about 80K out of it.
I have a b-tree index on column cola (varchar(255) ) for my where clause to use.
my "select count(*) from test where cola = 'abc' runs very fast,
but my actual "delete from test where cola = 'abc';" takes forever, never can finish and I haven't figured why....
In my explain output, what is that "Bitmap Heap Scan on table"? is it a table scan? is my index being used?
How does delete work? to delete 80K rows that meet my condition, does Postgres find them all and delete them all together or one at a time?
by the way, there is a foreign key on another table that references the primary key col0 on table test.
Could some one help me out here?
Thanks a lot,
Jessica
testdb=# select count(*) from test;
count
--------
295793 --total 295,793 rows
(1 row)
Time: 155.079 ms
testdb=# select count(*) from test where cola = 'abc';
count
-------
80998 - need to delete 80,988 rows
(1 row)
testdb=# explain delete from test where cola = 'abc';
QUERY PLAN
----------------------------------------------------------------------------------------------------
Bitmap Heap Scan on test (cost=2110.49..10491.57 rows=79766 width=6)
Recheck Cond: ((cola)::text = 'abc'::text)
-> Bitmap Index Scan on test_cola_idx (cost=0.00..2090.55 rows=79766 width=0)
Index Cond: ((cola)::text = 'abc'::text)
(4 rows)
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: rjessil@yahoo.com
Subject: Re: slow delete
In-Reply-To: <357892.18257.qm@web56412.mail.re3.yahoo.com>
* 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