From: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | "Dimi Paun" <dimi(at)lattica(dot)com> |
Cc: | pgsql-performance <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Bad performance on simple query |
Date: | 2008-11-17 17:16:32 |
Message-ID: | dcc563d10811170916n622e4f86g8f2b2dbe9b9e2a61@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Mon, Nov 17, 2008 at 10:07 AM, Dimi Paun <dimi(at)lattica(dot)com> wrote:
>
> On Mon, 2008-11-17 at 09:53 -0700, Scott Marlowe wrote:
>>
>> Are you saying it's excessive you need the compound query? Cause
>> that's running in 91microseconds as pointed out by Alan.
>
> Of course, my bad. I read that as 91ms (<blush/>).
>
> Confusion came from the fact that pgadminIII reports the query
> taking 20-40ms, so I read the 0.091 as seconds not ms.
Ahhh. Keep in mind that if you just run the query, pgadminIII will
tell you how long it took to run AND return all the data across the
network, so it will definitely take longer then. But most of that's
network io wait so it's not a real issue unless you're saturating your
network.
From | Date | Subject | |
---|---|---|---|
Next Message | Dimi Paun | 2008-11-17 17:31:02 | Re: Bad performance on simple query |
Previous Message | Dimi Paun | 2008-11-17 17:07:01 | Re: Bad performance on simple query |