Re: Different query plans on same servers

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Mario Splivalo" <mario(dot)splivalo(at)megafon(dot)hr>
Cc: "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: Different query plans on same servers
Date: 2011-12-06 20:17:30
Message-ID: 4EDE23FA020000250004393F@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> I'd wonder first if you have the same statistics settings on both.
> The big problem here is that the estimation of the join size is
> bad (8588 versus 0).

But both servers develop that estimate for the join size. I was
wondering more about whether the costing factors were really the
same:

slow:

-> Nested Loop
(cost=0.00..792824.51 rows=8588 width=275)
(actual time=3269.997..3269.997 rows=0 loops=1)

versus fast:

-> Hash Join
(cost=857.00..31152.80 rows=8588 width=275)
(actual time=37.968..37.968 rows=0 loops=1)

The hash join path must look more expensive on the first machine,
for some reason.

Mario, could you post the result of running this query from both
servers?:

http://wiki.postgresql.org/wiki/Server_Configuration

-Kevin

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Kevin Grittner 2011-12-06 20:29:03 Re: Different query plans on same servers
Previous Message Tom Lane 2011-12-06 20:00:49 Re: Different query plans on same servers