From: | Craig Ringer <ringerc(at)ringerc(dot)id(dot)au> |
---|---|
To: | Sylvain CAILLET <scaillet(at)alaloop(dot)com> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Slow Delete : Seq scan instead of index scan |
Date: | 2012-10-16 08:09:21 |
Message-ID: | 507D1631.9050904@ringerc.id.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On 10/16/2012 03:50 PM, Sylvain CAILLET wrote:
> 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.
Can you post that (or paste to explain.depesz.com and link to it here)
along with a "\d tablename" from psql?
--
Craig Ringer
From | Date | Subject | |
---|---|---|---|
Next Message | Sylvain CAILLET | 2012-10-16 08:13:10 | Re: Slow Delete : Seq scan instead of index scan |
Previous Message | Sékine Coulibaly | 2012-10-16 08:01:01 | Re: Slow Delete : Seq scan instead of index scan |