| From: | Karim Nassar <karim(dot)nassar(at)acm(dot)org> |
|---|---|
| To: | Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(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-26 19:36:28 |
| Message-ID: | 1111865788.9172.13.camel@k2.cet.nau.edu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Sat, 2005-03-26 at 07:55 -0800, Stephan Szabo wrote:
> That seems like it should be okay, hmm, what does something like:
>
> PREPARE test(int) AS SELECT 1 from measurement where
> id_int_sensor_meas_type = $1 FOR UPDATE;
> EXPLAIN ANALYZE EXECUTE TEST(1);
>
> give you as the plan?
QUERY PLAN
-----------------------------------------------------------------------------------------------------------------------
Seq Scan on measurement (cost=0.00..164559.16 rows=509478 width=6)
(actual time=11608.402..11608.402 rows=0 loops=1)
Filter: (id_int_sensor_meas_type = $1)
Total runtime: 11608.441 ms
(3 rows)
--
Karim Nassar
Department of Computer Science
Box 15600, College of Engineering and Natural Sciences
Northern Arizona University, Flagstaff, Arizona 86011
Office: (928) 523-5868 -=- Mobile: (928) 699-9221
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2005-03-26 20:55:58 | Re: How to improve db performance with $7K? |
| Previous Message | Stephan Szabo | 2005-03-26 15:55:39 | Re: Delete query takes exorbitant amount of time |