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

Re: simple update queries take a long time - postgres 8.3.1

From: mark <markkicks(at)gmail(dot)com>
To: rod(at)iol(dot)ie
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: simple update queries take a long time - postgres 8.3.1
Date: 2008-03-31 19:51:10
Message-ID: 82fa9e310803311251l77446816re1f039ac7da6b9ca@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-general
On Mon, Mar 31, 2008 at 12:48 PM, Raymond O'Donnell <rod(at)iol(dot)ie> wrote:

> On 31/03/2008 20:38, mark wrote:
>
> > EXPLAIN ANALYZE update users set number_recieved=number_recieved+1 where
> > uid=738889333;
> >                                                     QUERY PLAN
> >
> ------------------------------------------------------------------------------------------------------------------
> >  Index Scan using idx_uid on users  (cost=0.00..8.46 rows=1 width=1073)
> > (actual time=0.094..0.161 rows=1 loops=1)
> >    Index Cond: (uid = 738889333)
> >  Total runtime: 11479.053 ms
>
> Is there anything going on that might affect the time taken? - triggers,
> loads of indices to be updated, etc? From the docs[1]:

no, there are no triggers at all.. just the index on the column..
can you explain what the numbers mean in the EXPLAIN ANALYZE?
(cost=0.00..8.46 rows=1 width=1073)  (actual time=0.094..0.161 rows=1
loops=1)
thanks

In response to

Responses

pgsql-general by date

Next:From: Tom LaneDate: 2008-03-31 19:52:46
Subject: Re: [HACKERS] ANALYZE getting dead tuple count hopelessly wrong
Previous:From: Raymond O'DonnellDate: 2008-03-31 19:49:08
Subject: Re: simple update queries take a long time - postgres 8.3.1

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