Re: Trying to track down weird query stalls

From: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
To: dan(at)sidhe(dot)org
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-performance(at)postgresql(dot)org
Subject: Re: Trying to track down weird query stalls
Date: 2009-03-30 19:47:17
Message-ID: dcc563d10903301247t58bef7cbsd0b6d3bbd1a5e046@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Mon, Mar 30, 2009 at 1:42 PM, <dan(at)sidhe(dot)org> wrote:
>> On Mon, Mar 30, 2009 at 12:42 PM,  <dan(at)sidhe(dot)org> wrote:
>>> Arguably in this case the actual query should run faster than the
>>> EXPLAIN
>>> ANALYZE version, since the cache is hot. (Though that'd only likely
>>> shave
>>> a few dozen ms off the runtime)
>>
>> Joining a lot of tables together?  Could be GEQO kicking in.
>
> Only if I get different query plans for the query depending on whether
> it's being EXPLAIN ANALYZEd or not. That seems unlikely...

Yes, you can. In fact you often will. Not because it's being
explained or not, just because that's how GEQO works.

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message dan 2009-03-30 20:02:28 Re: Trying to track down weird query stalls
Previous Message dan 2009-03-30 19:42:25 Re: Trying to track down weird query stalls