X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id CB406D1B56B for ; Mon, 29 Sep 2003 18:21:58 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 45935-01 for ; Mon, 29 Sep 2003 15:21:31 -0300 (ADT) Received: from davinci.ethosmedia.com (unknown [209.128.84.228]) by svr1.postgresql.org (Postfix) with ESMTP id D1395D1B582 for ; Mon, 29 Sep 2003 15:21:19 -0300 (ADT) Received: from [63.195.55.98] (HELO spooky) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.0.2) with ESMTP id 3695174; Mon, 29 Sep 2003 11:12:26 -0700 Content-Type: text/plain; charset="iso-8859-1" From: Josh Berkus Organization: Aglio Database Solutions To: Oleg Lebedev , Mary Edie Meredith Subject: Re: TPC-R benchmarks Date: Mon, 29 Sep 2003 11:11:11 -0700 User-Agent: KMail/1.4.3 Cc: Jenny Zhang , pgsql-performance References: <993DBE5B4D02194382EC8DF8554A52731D75EC@postoffice.waterford.org> In-Reply-To: <993DBE5B4D02194382EC8DF8554A52731D75EC@postoffice.waterford.org> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <200309291111.11191.josh@agliodbs.com> X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200309/372 X-Sequence-Number: 3738 Oleg, > I just checked the restrictions on the TPC-R and TPC-H schemas and it > seems that all indexes are allowed in TPC-R and only those that index > parts of primary or foreign keys are allowed in TPC-H. That would be appropriate for this case though, yes? That column is part of a foriegn key, unless I've totally lost track. As I remarked before, Postgres does *not* automatically create indexes for FKs. Many, but not all, other database products do, so comparing PostgreSQL against those products without the index is unfair. -- Josh Berkus Aglio Database Solutions San Francisco