Re: TPC-R benchmarks - Mailing list pgsql-performance

From Oleg Lebedev
Subject Re: TPC-R benchmarks
Date
Msg-id 993DBE5B4D02194382EC8DF8554A52731D75EE@postoffice.waterford.org
Whole thread Raw
In response to TPC-R benchmarks  (Oleg Lebedev <oleg.lebedev@waterford.org>)
List pgsql-performance
Yes Josh,
L_partkey is a part of the foreign key on the Lineitem table, and it was
ok to create an index on it according to the TPC-R specs. I just created
indices on the rest of the FK columns in the TPC-R database and will
continue my evaluations.
Thanks.

Oleg

-----Original Message-----
From: Josh Berkus [mailto:josh@agliodbs.com]
Sent: Monday, September 29, 2003 12:11 PM
To: Oleg Lebedev; Mary Edie Meredith
Cc: Jenny Zhang; pgsql-performance
Subject: Re: [PERFORM] TPC-R benchmarks


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

*************************************

This e-mail may contain privileged or confidential material intended for the named recipient only.
If you are not the named recipient, delete this message and all attachments.
Unauthorized reviewing, copying, printing, disclosing, or otherwise using information in this e-mail is prohibited.
We reserve the right to monitor e-mail sent through our network.

*************************************

pgsql-performance by date:

Previous
From: Josh Berkus
Date:
Subject: Re: TPC-R benchmarks
Next
From: "scott.marlowe"
Date:
Subject: Re: advice on raid controller