Re: 512,600ms query becomes 7500ms... but why? Postgres 8.3 query planner quirk?

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Karl Denninger" <karl(at)denninger(dot)net>
Cc: "Bryce Nesbitt" <bryce2(at)obviously(dot)com>, <pgsql-performance(at)postgresql(dot)org>
Subject: Re: 512,600ms query becomes 7500ms... but why? Postgres 8.3 query planner quirk?
Date: 2010-02-12 16:54:27
Message-ID: 4B753363020000250002F259@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Karl Denninger <karl(at)denninger(dot)net> wrote:
> Kevin Grittner wrote:

>> Have you seen such a difference under 8.4? Can you provide a
>> self-contained example?

> Yes:
>
> [query and EXPLAIN ANALYZE of fast query]

> The alternative:
>
> [query with no other information]
>
> goes nuts.

Which means what? Could you post an EXPLAIN ANALYZE, or at least an
EXPLAIN, of the slow version? Can you post the table structure,
including indexes?

-Kevin

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Tom Lane 2010-02-12 18:20:29 Re: Questions on plan with INSERT/SELECT on partitioned table
Previous Message Karl Denninger 2010-02-12 16:43:10 Re: 512,600ms query becomes 7500ms... but why? Postgres 8.3 query planner quirk?