From: Tom Lane <tgl@sss.pgh.pa.us>
To: Miguel Arroz <arroz@guiamac.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: UPDATE 66k rows too slow
Date: Mon, 10 Mar 2008 00:48:54 -0400
Message-ID: <28948.1205124534@sss.pgh.pa.us> (raw)
In-Reply-To: <879F65BD-D1B0-4D15-BAE3-056305B84474@guiamac.com>
References: <879F65BD-D1B0-4D15-BAE3-056305B84474@guiamac.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, arroz@guiamac.com
Subject: Re: UPDATE 66k rows too slow
In-Reply-To: <28948.1205124534@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox