X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 4473C3A49B0 for ; Thu, 4 Nov 2004 22:58:59 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 60112-05 for ; Thu, 4 Nov 2004 22:58:53 +0000 (GMT) Received: from bayswater1.ymogen.net (host-154-240-27-217.pobox.net.uk [217.27.240.154]) by svr1.postgresql.org (Postfix) with ESMTP id BBBA23A49B1 for ; Thu, 4 Nov 2004 22:58:55 +0000 (GMT) Received: from [82.68.132.233] (82-68-132-233.dsl.in-addr.zen.co.uk [82.68.132.233]) by bayswater1.ymogen.net (Postfix) with ESMTP id 82CD0A4111; Thu, 4 Nov 2004 22:58:55 +0000 (GMT) Message-ID: <418AB42F.3080505@ymogen.net> Date: Thu, 04 Nov 2004 22:58:55 +0000 From: Matt Clark User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: al_nunes@atua.com.br Cc: pgsql-performance@postgresql.org Subject: Re: Better Hardware, worst Results References: <1099602361.7775.15.camel@localhost> <1099602998.1647.711.camel@home> <1099608123.418ab03ba292f@webmail.atua.com.br> In-Reply-To: <1099608123.418ab03ba292f@webmail.atua.com.br> Content-Type: multipart/alternative; boundary="------------080506050205060805090403" X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=1.0 tagged_above=0.0 required=5.0 tests=HTML_20_30, HTML_MESSAGE, HTML_TITLE_EMPTY X-Spam-Level: * X-Archive-Number: 200411/71 X-Sequence-Number: 9025 This is a multi-part message in MIME format. --------------080506050205060805090403 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit al_nunes@atua.com.br wrote: >Citando Rod Taylor : > > >>Please send an explain analyze from both. >> >> >I'm sendin three explains. In the first the Dell machine didn't use existing >indexes, so I turn enable_seqscan off (this is the second explain). The total >cost decreased, but the total time not. The third explain refers to the cheaper >(and faster) machine. The last thing is the query itself. > > > Nested Loop (cost=9008.68..13596.97 rows=1 width=317) (actual >time=9272.803..65287.304 rows=2604 loops=1) > Nested Loop (cost=5155.51..19320.20 rows=1 width=317) (actual >time=480.311..62530.121 rows=2604 loops=1) > Hash Join (cost=2.23..11191.77 rows=9 width=134) (actual >time=341.708..21868.167 rows=2604 loops=1) > > > Well the plan is completely different on the dev machine. Therefore either the PG version or the postgresql.conf is different. No other possible answer. M --------------080506050205060805090403 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit

al_nunes@atua.com.br wrote:
Citando Rod Taylor <pg@rbt.ca>:
  
Please send an explain analyze from both.
    
I'm sendin three explains. In the first the Dell machine didn't use existing
indexes, so I turn enable_seqscan off (this is the second explain). The total
cost decreased, but the total time not. The third explain refers to the cheaper
(and faster) machine. The last thing is the query itself.


 Nested Loop  (cost=9008.68..13596.97 rows=1 width=317) (actual
time=9272.803..65287.304 rows=2604 loops=1)
 Nested Loop  (cost=5155.51..19320.20 rows=1 width=317) (actual
time=480.311..62530.121 rows=2604 loops=1)
 Hash Join  (cost=2.23..11191.77 rows=9 width=134) (actual
time=341.708..21868.167 rows=2604 loops=1)

  
Well the plan is completely different on the dev machine.  Therefore either the PG version or the postgresql.conf is different.  No other possible answer.

M
--------------080506050205060805090403--