From: | Mark Kirkwood <markir(at)paradise(dot)net(dot)nz> |
---|---|
To: | "Michael Ryan S(dot) Puncia" <mpuncia(at)census(dot)gov(dot)ph> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: DB Design |
Date: | 2004-05-20 09:28:28 |
Message-ID: | 40AC7A3C.2050001@paradise.net.nz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
The complete answer is probably "it depends", but this does not help
much...:-)
I would try out the simple approach first (i.e one 50 million row
table), but read up about :
i) partial indexes and maybe
ii) clustering
iii) think about presorting the data before loading to place "likely to
be accessed" rows "close" together in the table (if possible).
iv) get to know the analyze, explain, explain analyze commands....
Best wishes
Mark
Michael Ryan S. Puncia wrote:
> Hi Guys,
>
>
>
> My question is .. which is better design
>
>
>
> 1. Single Table with 50 million records or
> 2. Multiple Table using inheritance to the parents table
>
>
>
>
>
> I will use this only for query purpose ..
>
>
>
> Thanks ..
>
>
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Marty Scholes | 2004-05-20 13:46:08 | Re: Hardware Platform |
Previous Message | Matthew T. O'Connor | 2004-05-20 05:10:14 | Re: Wierd context-switching issue on Xeon |