Re: Delete query takes exorbitant amount of time
От | Stephan Szabo |
---|---|
Тема | Re: Delete query takes exorbitant amount of time |
Дата | |
Msg-id | 20050328082645.X95787@megazone.bigpanda.com обсуждение исходный текст |
Ответ на | Delete query takes exorbitant amount of time (Karim Nassar <Karim.Nassar@acm.org>) |
Ответы |
Re: Delete query takes exorbitant amount of time
|
Список | pgsql-performance |
On Mon, 28 Mar 2005, Karim A Nassar wrote: > On Mon, 28 Mar 2005, Simon Riggs wrote: > > run the EXPLAIN after doing > > SET enable_seqscan = off > > The results I previously supplied were searching for a non-existent > value, so I have provided output for both cases. > > *** > *** Searching for non-existent value > *** > > 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); > QUERY PLAN > -------------------------------------------------------------------------- > Seq Scan on measurement > (cost=0.00..164559.16 rows=509478 width=6) > (actual time=6421.849..6421.849 rows=0 loops=1) > Filter: (id_int_sensor_meas_type = $1) > Total runtime: 6421.917 ms > (3 rows) > > orfs=# SET enable_seqscan = off; I think you have to prepare with enable_seqscan=off, because it effects how the query is planned and prepared.
В списке pgsql-performance по дате отправления: