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

From: Raymond O'Donnell <rod(at)iol(dot)ie>
To: mark <markkicks(at)gmail(dot)com>
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:59:43
Message-ID: 47F142AF.1050109@iol.ie
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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)

It's worth reading through the docs at that reference in my previous
email - it's well explained there.

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.

Ray.

---------------------------------------------------------------
Raymond O'Donnell, Director of Music, Galway Cathedral, Ireland
rod(at)iol(dot)ie
---------------------------------------------------------------

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message mark 2008-03-31 20:03:29 Re: simple update queries take a long time - postgres 8.3.1
Previous Message Tom Lane 2008-03-31 19:52:46 Re: [HACKERS] ANALYZE getting dead tuple count hopelessly wrong