pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: dan@sidhe.org
To: Scott Marlowe <scott.marlowe@gmail.com>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Trying to track down weird query stalls
Date: Mon, 30 Mar 2009 15:42:25 -0400 (EDT)
Message-ID: <57654.199.172.169.17.1238442145.squirrel@localhost> (raw)
In-Reply-To: <dcc563d10903301238u135d82bpf498c2d40ac31977@mail.gmail.com>
References: <58166.199.172.169.15.1238435452.squirrel@localhost>
	<603c8f070903301131p8086067ob552d09e8b21c82@mail.gmail.com>
	<56921.199.172.169.36.1238438533.squirrel@localhost>
	<dcc563d10903301238u135d82bpf498c2d40ac31977@mail.gmail.com>

> On Mon, Mar 30, 2009 at 12:42 PM,  <dan@sidhe.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...

-Dan



view thread (19+ messages)  latest in thread

Message-ID: <57654.199.172.169.17.1238442145.squirrel@localhost>
Permalink:  ../57654.199.172.169.17.1238442145.squirrel@localhost/
Also on:    postgresql.org/message-id/57654.199.172.169.17.1238442145.squirrel@localhost

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: dan@sidhe.org, scott.marlowe@gmail.com, robertmhaas@gmail.com
  Subject: Re: Trying to track down weird query stalls
  In-Reply-To: <57654.199.172.169.17.1238442145.squirrel@localhost>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox