Skip site navigation (1) Skip section navigation (2)

Re: Delete query takes exorbitant amount of time

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: Karim A Nassar <Karim(dot)Nassar(at)NAU(dot)EDU>
Cc: Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com>,Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>,Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>,pgsql-performance(at)postgresql(dot)org
Subject: Re: Delete query takes exorbitant amount of time
Date: 2005-03-28 19:25:54
Message-ID: 1112037954.11750.903.camel@localhost.localdomain (view raw or flat)
Thread:
Lists: pgsql-performance
On Mon, 2005-03-28 at 09:37 -0700, Karim A Nassar wrote:
> On Mon, 28 Mar 2005, Stephan Szabo wrote:
> > > On Mon, 28 Mar 2005, Simon Riggs wrote:
> > > > run the EXPLAIN after doing
> > > > 	SET enable_seqscan = off
> 
> ...
> 
> > I think you have to prepare with enable_seqscan=off, because it
> > effects how the query is planned and prepared.
> 
> orfs=# SET enable_seqscan = off;
> SET
> orfs=# PREPARE test2(int) AS SELECT 1 from measurement where
> orfs-# id_int_sensor_meas_type = $1 FOR UPDATE;
> PREPARE
> orfs=#  EXPLAIN ANALYZE EXECUTE TEST2(1); -- non-existent
> 
> QUERY PLAN                                       
> -------------------------------------------------------------------------
>  Index Scan using measurement__id_int_sensor_meas_type_idx on measurement
>     (cost=0.00..883881.49 rows=509478 width=6) 
>     (actual time=29.207..29.207 rows=0 loops=1)
>    Index Cond: (id_int_sensor_meas_type = $1)
>  Total runtime: 29.277 ms
> (3 rows)
> 
> orfs=#  EXPLAIN ANALYZE EXECUTE TEST2(197); -- existing value
> 
> QUERY PLAN                                   
> -------------------------------------------------------------------------
>  Index Scan using measurement__id_int_sensor_meas_type_idx on measurement
>     (cost=0.00..883881.49 rows=509478 width=6) 
>     (actual time=12.903..37478.167 rows=509478 loops=1)
>    Index Cond: (id_int_sensor_meas_type = $1)
>  Total runtime: 38113.338 ms
> (3 rows)
> 

"That process starts upon the supposition that when you have eliminated
all which is impossible, then whatever remains, however improbable, must
be the truth." - Sherlock Holmes

Well, based upon the evidence so far, the Optimizer got it right:

Normal
SeqScan, value=1	elapsed= 6.4s	cost=164559
SeqScan, value=197	elapsed=28.1s	cost=164559

SeqScan=off
IndexScan, value=1	elapsed= 29ms	cost=883881
IndexScan, value=197	elapsed=38.1s	cost=883881

With SeqScan=off the index is used, proving that it has been correctly
defined for use in queries.

The FK CASCADE delete onto measurement will only be triggered by the
deletion of a real row, so the actual value will be the time taken. This
is longer than a SeqScan, so the Optimizer is correct.

My guess is that Measurement has a greatly non-uniform distribution of
values and that 197 is one of the main values. Other values exist in the
lookup table, but are very infrequently occurring in the larger table.

Karim,
Please do:

select id_int_sensor_meas_type, count(*)
from measurement
group by id_int_sensor_meas_type
order by count(*) desc;

Best Regards, Simon Riggs



In response to

Responses

pgsql-performance by date

Next:From: Josh BerkusDate: 2005-03-28 19:51:17
Subject: Re: Query Optimizer Failure / Possible Bug
Previous:From: Joshua D. DrakeDate: 2005-03-28 18:39:48
Subject: Re: Sluggish server performance

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group