From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Miguel Arroz <arroz(at)guiamac(dot)com> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: UPDATE 66k rows too slow |
Date: | 2008-03-10 04:48:54 |
Message-ID: | 28948.1205124534@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Miguel Arroz <arroz(at)guiamac(dot)com> writes:
> EXPLAIN ANALYZE UPDATE text_answer_mapping_ebt SET f1 = false;
> QUERY PLAN
> -----------------------------------------------------------------------------------------------------------------------------------
> Seq Scan on text_answer_mapping_ebt (cost=0.00..13945.72
> rows=265072 width=92) (actual time=21.123..1049.054 rows=66268 loops=1)
> Total runtime: 63235.363 ms
> (2 rows)
Hm, only one second to do the scan ...
I'm thinking the extra time must be going into index updating or
CHECK-constraint checking or some such overhead. Can we see the full
schema definition of the table?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Smith | 2008-03-10 05:10:21 | Re: UPDATE 66k rows too slow |
Previous Message | andrew | 2008-03-10 04:10:10 | Re: UPDATE 66k rows too slow |