From: | Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com> |
---|---|
To: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
Cc: | Will Platnick <wplatnick(at)gmail(dot)com>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Slow Query Help |
Date: | 2013-02-06 16:27:37 |
Message-ID: | CABOikdO7VDWNDPF+ahAK0s0VapO4eQikT31X=58rcyMMiADiBw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Wed, Feb 6, 2013 at 9:52 PM, Kevin Grittner <kgrittn(at)ymail(dot)com> wrote:
> Will Platnick <wplatnick(at)gmail(dot)com> wrote:
>> Will Platnick <wplatnick(at)gmail(dot)com> wrote:
>
>>> The only thing that stands out is: on your production server I see
>>> "Total runtime: 7.515 ms", but the top node in EXPLAIN ANAYZE shows
>>> actual time as 0.179 ms. Not sure where that additional time is being
>>> spent though. It could be ExecutorStart/End, but have no idea why they
>>> should take so long.
>
>> Any ideas on how to troubleshoot this delay?
>
> Is the client which is running the query on the same machine as the
> server? If not, what's the ping time between them?
>
I don't think the network latency can cause that. The "Total runtime"
is calculated on the server side itself - see ExplainOnePlan().
Thanks,
Pavan
--
Pavan Deolasee
http://www.linkedin.com/in/pavandeolasee
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Krupka | 2013-02-06 18:20:14 | Re: postgresql.conf recommendations |
Previous Message | Will Platnick | 2013-02-06 16:24:34 | Re: Slow Query Help |