Received: from localhost (maia-3.hub.org [200.46.204.184])
	by postgresql.org (Postfix) with ESMTP id B47399FA274
	for <pgsql-performance-postgresql.org@postgresql.org>;
	Thu, 14 Dec 2006 12:51:08 -0400 (AST)
Received: from postgresql.org ([200.46.204.71])
	by localhost (mx1.hub.org [200.46.204.184]) (amavisd-new, port 10024)
	with ESMTP id 31157-07 for
	<pgsql-performance-postgresql.org@postgresql.org>;
	Thu, 14 Dec 2006 12:51:00 -0400 (AST)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.4
Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130])
	by postgresql.org (Postfix) with ESMTP id E1A2F9FA173
	for <pgsql-performance@postgresql.org>;
	Thu, 14 Dec 2006 12:51:00 -0400 (AST)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id kBEGoQtA021628;
	Thu, 14 Dec 2006 11:50:27 -0500 (EST)
To: Mark Lewis <mark.lewis@mir3.com>
cc: Arnaud Lesauvage <thewild@freesurf.fr>, Ragnar <gnari@hive.is>,
	Jens Schipkowski <jens.schipkowski@apus.co.at>,
	pgsql-performance@postgresql.org
Subject: Re: Slow update with simple query 
In-reply-to: <1166114095.27428.133.camel@archimedes> 
References: <457FDB1E.6040801@freesurf.fr>
 <op.tkhy4jpg81rjf6@xjens.apus.local>
	<457FF0CD.4050606@freesurf.fr> <op.tkh10qgw81rjf6@xjens.apus.local>
	<4580025D.2040903@freesurf.fr>
	<1166021340.6369.103.camel@localhost.localdomain>
	<45801A1B.6070200@freesurf.fr> <8399.1166028385@sss.pgh.pa.us>
	<4581593E.8080401@freesurf.fr> <20426.1166109494@sss.pgh.pa.us>
	<45816C54.5010602@freesurf.fr> <21233.1166113140@sss.pgh.pa.us>
	<1166114095.27428.133.camel@archimedes>
Comments: In-reply-to Mark Lewis <mark.lewis@mir3.com>
	message dated "Thu, 14 Dec 2006 08:34:55 -0800"
Date: Thu, 14 Dec 2006 11:50:26 -0500
Message-ID: <21627.1166115026@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Archive-Number: 200612/378
X-Sequence-Number: 22434

Mark Lewis <mark.lewis@mir3.com> writes:
> Out of curiosity, how hard would it be to modify the output of EXPLAIN
> ANALYZE when doing an insert/update to include the index update times
> and/or non-FK constraint checking times and/or the table row update
> times?

I don't think it'd help much --- in an example like this, other tools
like vmstat would be more likely to be useful in investigating the
problem.  There's also the problem that EXPLAIN ANALYZE overhead is
already too high --- another dozen gettimeofday() calls per row
processed doesn't sound appetizing.

			regards, tom lane