From: | Sylvain CAILLET <scaillet(at)alaloop(dot)com> |
---|---|
To: | pgsql-performance(at)postgresql(dot)org |
Subject: | Slow Delete : Seq scan instead of index scan |
Date: | 2012-10-16 07:50:12 |
Message-ID: | 1837771448.3789694.1350373812378.JavaMail.root@alaloop.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Hi to all,
I've got a trouble with some delete statements. My db contains a little more than 10000 tables and runs on a dedicated server (Debian 6 - bi quad - 16Gb - SAS disks raid 0). Most of the tables contains between 2 and 3 million rows and no foreign keys exist between them. Each is indexed (btree) on start_date / end_date fields (bigint). The Postgresql server has been tuned (I can give modified values if needed).
I perform recurrent DELETE upon a table subset (~1900 tables) and each time, I delete a few lines (between 0 and 1200). Usually it takes between 10s and more than 2mn. It seems to me to be a huge amount of time ! An EXPLAIN ANALYZE on a DELETE shows me that the planner uses a Seq Scan instead of an Index Scan. Autovaccum is on and I expect the db stats to be updated in real time (pg_stats file is stored in /dev/shm RAM disk for quick access).
Do you have any idea about this trouble ?
Sylvain Caillet
Bureau : + 33 5 59 41 51 10
scaillet(at)alaloop(dot)com
ALALOOP S.A.S. - Technopole Izarbel - 64210 Bidart
www.alaloop.com
From | Date | Subject | |
---|---|---|---|
Next Message | Sékine Coulibaly | 2012-10-16 08:01:01 | Re: Slow Delete : Seq scan instead of index scan |
Previous Message | Marinos Yannikos | 2012-10-16 05:07:14 | Re: Two identical systems, radically different performance |