Re: UPDATE 66k rows too slow - Mailing list pgsql-performance

From Tom Lane
Subject Re: UPDATE 66k rows too slow
Date
Msg-id 28948.1205124534@sss.pgh.pa.us
Whole thread Raw
In response to UPDATE 66k rows too slow  (Miguel Arroz <arroz@guiamac.com>)
List pgsql-performance
Miguel Arroz <arroz@guiamac.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

pgsql-performance by date:

Previous
From: andrew@pillette.com
Date:
Subject: Re: UPDATE 66k rows too slow
Next
From: Greg Smith
Date:
Subject: Re: UPDATE 66k rows too slow