X-Original-To: pgsql-performance-postgresql.org@postgresql.org
Received: from localhost (wm.hub.org [200.46.204.128])
	by postgresql.org (Postfix) with ESMTP id 2ACE79FA38D
	for <pgsql-performance-postgresql.org@postgresql.org>;
	Thu, 10 Aug 2006 16:02:30 -0300 (ADT)
Received: from postgresql.org ([200.46.204.71])
	by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024)
	with ESMTP id 31822-10 for
	<pgsql-performance-postgresql.org@postgresql.org>;
	Thu, 10 Aug 2006 19:02:18 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-
Received: from hs5.cfa.cmu.edu (HS5.CFA.cmu.edu [128.2.103.215])
	by postgresql.org (Postfix) with ESMTP id B65E09FB2FA
	for <pgsql-performance@postgresql.org>;
	Thu, 10 Aug 2006 16:02:13 -0300 (ADT)
Received: from [192.168.100.102] (host82.155.212.198.conversent.net
	[155.212.198.82]) (authenticated bits=0)
	by hs5.cfa.cmu.edu (8.12.11.20060308/8.12.11) with ESMTP id
	k7AJ2BIq006584
	(version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO)
	for <pgsql-performance@postgresql.org>; Thu, 10 Aug 2006 15:02:12 -0400
Mime-Version: 1.0 (Apple Message framework v752.2)
In-Reply-To: <20060803233939.75401.qmail@web30304.mail.mud.yahoo.com>
References: <20060803233939.75401.qmail@web30304.mail.mud.yahoo.com>
Content-Type: multipart/alternative; boundary=Apple-Mail-12-835670872
Message-Id: <E4580219-F2D4-4DBD-8203-E373860EDDEF@themactionfaction.com>
From: AgentM <agentm@themactionfaction.com>
Subject: Re: slow transfer speeds with PostgreSQL
Date: Thu, 10 Aug 2006 15:02:09 -0400
To: pgsql-performance@postgresql.org
X-Mailer: Apple Mail (2.752.2)
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=0.135 tagged_above=0 required=5 tests=HTML_50_60,
	HTML_MESSAGE
X-Spam-Level: 
X-Archive-Number: 200608/196
X-Sequence-Number: 20381


--Apple-Mail-12-835670872
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=US-ASCII;
	delsp=yes;
	format=flowed


On Aug 3, 2006, at 19:39 , hansell baran wrote:
> When we run the following query "SELECT * FROM big_table", we get  
> the following resutls:
> Very different results are obtained if a the query "SELECT * from  
> big_table ORDER BY "some_column"". In this scenario

You should perform your test with queries which are identical or  
similar to the queries which the database will really be seeing.  
Anything else isn't really relevant for tuning because different  
configurations cater to different types of workloads.

-M
--Apple-Mail-12-835670872
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=ISO-8859-1

<HTML><BODY style=3D"word-wrap: break-word; -khtml-nbsp-mode: space; =
-khtml-line-break: after-white-space; "><BR><DIV><DIV>On Aug 3, 2006, at =
19:39 , hansell baran wrote:</DIV><BLOCKQUOTE type=3D"cite"><P =
style=3D"margin: 0.0px 0.0px 0.0px 0.0px"><FONT face=3D"Helvetica" =
size=3D"3" style=3D"font: 12.0px Helvetica">When we run the following =
query "SELECT * FROM big_table", we get the following =
resutls:</FONT></P> <P style=3D"margin: 0.0px 0.0px 0.0px 0.0px"><FONT =
face=3D"Helvetica" size=3D"3" style=3D"font: 12.0px Helvetica">Very =
different results are obtained if a the query "SELECT * from big_table =
ORDER BY "some_column"". In this scenario<SPAN =
class=3D"Apple-converted-space">=A0</SPAN></FONT></P> =
</BLOCKQUOTE></DIV><BR><DIV>You should perform your test with queries =
which are identical or similar to the queries which the database will =
really be seeing. Anything else isn't really relevant for tuning because =
different configurations cater to different types of =
workloads.=A0</DIV><DIV><BR =
class=3D"khtml-block-placeholder"></DIV><DIV>-M</DIV></BODY></HTML>=

--Apple-Mail-12-835670872--