Re: performance penalty between Postgresql 8.3.8 and 8.4.1

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "David Schmitz" <david(dot)schmitz(at)harman(dot)com>, <pgsql-performance(at)postgresql(dot)org>
Subject: Re: performance penalty between Postgresql 8.3.8 and 8.4.1
Date: 2009-12-07 22:19:51
Message-ID: 4B1D2B27020000250002D18A@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

"Schmitz, David" <david(dot)schmitz(at)harman(dot)com> wrote:

> It is carried out with poor performance on postgresql 8.4.1
> However postgresql 8.3.8 performs just fine.
> If you take a closer look at the query with EXPLAIN, it becomes
> obvious, that postgresql 8.4 does not consider the primary key at
> level 3 and instead generates a hash join:

> Postgresql 8.4.1:
>
> Sort (cost=129346.71..129498.64 rows=60772 width=61)

> Postgresql 8.3.8:
>
> Sort (cost=3792.75..3792.95 rows=81 width=61)

It determines the plan based on available statistics, which in this
case seem to indicate rather different data. Do the two databases
have identical data? Have they both been recently analyzed? What
is the default_statistics_target on each? Do any columns in these
tables have overrides?

-Kevin

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Karl Denninger 2009-12-07 22:31:44 Re: RAID card recommendation
Previous Message Schmitz, David 2009-12-07 22:05:14 performance penalty between Postgresql 8.3.8 and 8.4.1