Skip site navigation (1) Skip section navigation (2)

Re: Slow update with simple query

From: Mark Lewis <mark(dot)lewis(at)mir3(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Arnaud Lesauvage <thewild(at)freesurf(dot)fr>, Ragnar <gnari(at)hive(dot)is>, Jens Schipkowski <jens(dot)schipkowski(at)apus(dot)co(dot)at>, pgsql-performance(at)postgresql(dot)org
Subject: Re: Slow update with simple query
Date: 2006-12-13 17:51:13
Message-ID: 1166032273.27428.98.camel@archimedes (view raw, whole thread or download thread mbox)
Lists: pgsql-performance
But he's using 8.1.4-- in that version, an explain analyze would list
the time taken to go through triggers, so the fact that we don't see any
of those lines means that it can't be constraint checking, so wouldn't
it have to be the index update overhead?

-- Mark

On Wed, 2006-12-13 at 11:46 -0500, Tom Lane wrote:
> Arnaud Lesauvage <thewild(at)freesurf(dot)fr> writes:
> > Indeed, the new query does not perform that well :
> > "Hash Join  (cost=112.75..307504.97 rows=2024869 width=355) (actual time=53.995..246443.811 rows=2020061 loops=1)"
> > ...
> > "Total runtime: 2777844.892 ms"
> > I removed all unnecessary indexes on t1 before running the query (I left the index on uid and the multicolumn index containind the updated field).
> > I believe the multicolumn-functional-index computation is taking some time here, isn't it ?
> Given that the plan itself only takes 246 sec, there's *something*
> associated with row insertion that's eating the other 2500+ seconds.
> Either index entry computation or constraint checking ...
> 			regards, tom lane
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Have you searched our list archives?

In response to


pgsql-performance by date

Next:From: RonDate: 2006-12-13 18:03:04
Subject: Re: New to PostgreSQL, performance considerations
Previous:From: Tom LaneDate: 2006-12-13 17:29:18
Subject: Re: Insertion to temp table deteriorating over time

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group