X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 4116AD1D52E for ; Thu, 22 Apr 2004 15:21:46 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 58883-10 for ; Thu, 22 Apr 2004 15:21:46 -0300 (ADT) Received: from web11.manitu.net (web11.manitu.net [217.11.48.111]) by svr1.postgresql.org (Postfix) with ESMTP id 52E61D1D2B7 for ; Thu, 22 Apr 2004 15:21:44 -0300 (ADT) Received: from [192.168.0.1] (dsl-082-082-191-254.arcor-ip.net [82.82.191.254]) (authenticated) by web11.manitu.net (8.10.2-SOL3/8.10.2) with ESMTP id i3MIKhM15894; Thu, 22 Apr 2004 20:20:43 +0200 Subject: Re: [pgsql-advocacy] MySQL vs PG TPC-H benchmarks From: Markus Bertheau To: Tom Lane Cc: Eduardo Almeida , Jan Wieck , Josh Berkus , pgsql-performance@postgresql.org In-Reply-To: <7444.1082649288@sss.pgh.pa.us> References: <20040422125318.26053.qmail@web60601.mail.yahoo.com> <7444.1082649288@sss.pgh.pa.us> Content-Type: text/plain; charset=UTF-8 Message-Id: <1082658047.4524.0.camel@yarrow.bertheau.de> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-1) Date: Thu, 22 Apr 2004 20:20:47 +0200 Content-Transfer-Encoding: quoted-printable X-Virus-Scanned: by amavisd-new at postgresql.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200404/388 X-Sequence-Number: 6688 =D0=92 =D0=A7=D1=82=D0=B2, 22.04.2004, =D0=B2 17:54, Tom Lane =D0=BF=D0=B8= =D1=88=D0=B5=D1=82: > Eduardo Almeida writes: > > About 7hs:30min to load the data and 16:09:25 to > > create the indexes >=20 > You could probably improve the index-create time by temporarily > increasing sort_mem. It wouldn't be unreasonable to give CREATE INDEX > several hundred meg to work in. (You don't want sort_mem that big > normally, because there may be many sorts happening in parallel, > but in a data-loading context there'll just be one active sort.) Doesn't this provide a reason for CREATE INDEX not to honour sort_mem? --=20 Markus Bertheau