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 20:11:01
Message-ID: 82fa9e310803311311q7a7ffe71qebab677b537a28e6@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Mar 31, 2008 at 12:59 PM, Raymond O'Donnell <rod(at)iol(dot)ie> wrote:

> On 31/03/2008 20:51, mark wrote:
>
> > 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)
>
> As I understand it, "cost" signifies the planner's estimate of how long
> the query will take, in terms of disk page fetches. The "actual time" is
> in milliseconds.

it says actual time is 0.161 seconds or milliseconds.. but the total run
time is 11 seconds.. any ideas why this discrepancy?

> 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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2008-03-31 20:27:32 Re: FATAL: bogus freespace amount
Previous Message mark 2008-03-31 20:03:29 Re: simple update queries take a long time - postgres 8.3.1