Re: Fast Inserts and Hardware Questions - Mailing list pgsql-general

From Orion Henry
Subject Re: Fast Inserts and Hardware Questions
Date
Msg-id 3AAFD176.3DFA200F@trustcommerce.com
Whole thread Raw
In response to Re: Fast Inserts and Hardware Questions  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: Fast Inserts and Hardware Questions  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-general
Peter Eisentraut wrote:
>
> Orion Henry writes:
>
> > The indexes will be
> > int8 (primary key)
> > int4 (group number)
> > timestamp (creation date)
> > int4 (customer id)
>
> Since one query can only use one index per table, you should only need the
> customer_id index, given the queries you listed.

Isn't that was multi-column indexes are for?

I have 100's of customers but millions of database entries.  If I have
to I'll make a table for each customer, big_table_5 and big_table_6
etc... but this seems to be a terrible hack and the database should be
able to do things like this for me.

Orion Henry
CTO TrustCommerce
orion@trustcommerce.com

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Case Insensitive CHECK CONSTRAINTs
Next
From: Jan Ploski
Date:
Subject: Re: Compiling 7.1 JDBC driver