Skip site navigation (1) Skip section navigation (2)

Re: DB Design

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 (view raw or flat)
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 ..
>
>  
>
>  
>

In response to

  • DB Design at 2004-05-19 07:37:06 from Michael Ryan S. Puncia

pgsql-performance by date

Next:From: Marty ScholesDate: 2004-05-20 13:46:08
Subject: Re: Hardware Platform
Previous:From: Matthew T. O'ConnorDate: 2004-05-20 05:10:14
Subject: Re: Wierd context-switching issue on Xeon

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group