Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 790DF2E028A for ; Mon, 10 Mar 2008 01:48:59 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 36087-07 for ; Mon, 10 Mar 2008 01:48:56 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 1586A2E0289 for ; Mon, 10 Mar 2008 01:48:55 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id m2A4mssB028949; Mon, 10 Mar 2008 00:48:54 -0400 (EDT) To: Miguel Arroz cc: pgsql-performance@postgresql.org Subject: Re: UPDATE 66k rows too slow In-reply-to: <879F65BD-D1B0-4D15-BAE3-056305B84474@guiamac.com> References: <879F65BD-D1B0-4D15-BAE3-056305B84474@guiamac.com> Comments: In-reply-to Miguel Arroz message dated "Mon, 10 Mar 2008 02:21:39 -0000" Date: Mon, 10 Mar 2008 00:48:54 -0400 Message-ID: <28948.1205124534@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200803/189 X-Sequence-Number: 29143 Miguel Arroz 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