From: Robert Haas <robertmhaas@gmail.com>
To: dan@sidhe.org
Cc: Scott Marlowe <scott.marlowe@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Trying to track down weird query stalls
Date: Mon, 30 Mar 2009 16:13:27 -0400
Message-ID: <603c8f070903301313u1a9606a3m27da187b5e376785@mail.gmail.com> (raw)
In-Reply-To: <56164.199.172.169.17.1238443348.squirrel@localhost>
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>
<57654.199.172.169.17.1238442145.squirrel@localhost>
<dcc563d10903301247t58bef7cbsd0b6d3bbd1a5e046@mail.gmail.com>
<56164.199.172.169.17.1238443348.squirrel@localhost>
On Mon, Mar 30, 2009 at 4:02 PM, <dan@sidhe.org> wrote:
>> On Mon, Mar 30, 2009 at 1:42 PM, <dan@sidhe.org> wrote:
>>>> 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...
>>
>> Yes, you can. In fact you often will. Not because it's being
>> explained or not, just because that's how GEQO works.
>
> Ouch. I did *not* know that was possible -- I assumed that the plan was
> deterministic and independent of explain analyze. The query has seven
> tables (one of them a temp table) and my geqo_threshold is set to 12. If
> I'm reading the docs right GEQO shouldn't kick in.
Any chance we could see the actual query? Right now I think we are
shooting in the dark.
...Robert
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: robertmhaas@gmail.com, dan@sidhe.org, scott.marlowe@gmail.com
Subject: Re: Trying to track down weird query stalls
In-Reply-To: <603c8f070903301313u1a9606a3m27da187b5e376785@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> <57654.199.172.169.17.1238442145.squirrel@localhost> <dcc563d10903301247t58bef7cbsd0b6d3bbd1a5e046@mail.gmail.com> <56164.199.172.169.17.1238443348.squirrel@localhost> <603c8f070903301313u1a9606a3m27da187b5e376785@mail.gmail.com>
* 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