Re: same query in high number of times

From: Laurent Laborde <kerdezixe(at)gmail(dot)com>
To: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
Cc: Peter Alban <peter(dot)alban2(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-performance(at)postgresql(dot)org
Subject: Re: same query in high number of times
Date: 2009-06-23 08:55:49
Message-ID: 8a1bfe660906230155y413b0e56w39d4b28e8bf993a4@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Tue, Jun 23, 2009 at 10:52 AM, Laurent Laborde<kerdezixe(at)gmail(dot)com> wrote:
> On Mon, Jun 22, 2009 at 12:06 AM, Scott Marlowe<scott(dot)marlowe(at)gmail(dot)com> wrote:
>> On Sun, Jun 21, 2009 at 12:28 PM, Peter Alban<peter(dot)alban2(at)gmail(dot)com> wrote:
>>> Hi,
>>>
>>> Here is the query  :
>>> duration: 2533.734 ms  statement:
>>
>> SNIP
>>
>>>  Limit  (cost=4313.54..4313.55 rows=3 width=595) (actual
>>> time=288.525..288.528 rows=3 loops=1)
>>
>> According to this query plan, your query is taking up 288
>> milliseconds.  I'm guessing the rest of the time is actually is spent
>> transferring data.
>
> Huuuuuu ...
> The cost is _certainly_ not the time in ms.
> See the planner cost constants in a config file, or in any good documentation.

Woooops... cost... time... my mistake ... :)
*duck and cover*

--
F4FQM
Kerunix Flan
Laurent Laborde

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Mathieu Nebra 2009-06-23 11:12:39 How would you store read/unread topic status?
Previous Message Laurent Laborde 2009-06-23 08:52:08 Re: same query in high number of times