Re: simple update queries take a long time - postgres 8.3.1 - Mailing list pgsql-general

From mark
Subject Re: simple update queries take a long time - postgres 8.3.1
Date
Msg-id 82fa9e310803311251l77446816re1f039ac7da6b9ca@mail.gmail.com
Whole thread Raw
In response to Re: simple update queries take a long time - postgres 8.3.1  (Raymond O'Donnell <rod@iol.ie>)
Responses Re: simple update queries take a long time - postgres 8.3.1  (Raymond O'Donnell <rod@iol.ie>)
Check if table or View exists  ("Jeff Williams" <jeff.williams@hardsoft.com.au>)
List pgsql-general
On Mon, Mar 31, 2008 at 12:48 PM, Raymond O'Donnell <rod@iol.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

pgsql-general by date:

Previous
From: Raymond O'Donnell
Date:
Subject: Re: simple update queries take a long time - postgres 8.3.1
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] ANALYZE getting dead tuple count hopelessly wrong