Miguel Arroz <arroz@xxxxxxxxxxx> 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 -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
