From: Mark Kirkwood <markir@paradise.net.nz>
To: Michael Ryan S. Puncia <mpuncia@census.gov.ph>
Cc: pgsql-performance@postgresql.org
Subject: Re: DB Design
Date: Thu, 20 May 2004 21:28:28 +1200
Message-ID: <40AC7A3C.2050001@paradise.net.nz> (raw)
In-Reply-To: <200405190724.i4J7NuPW030497@mail.census.gov.ph>
References: <200405190724.i4J7NuPW030497@mail.census.gov.ph>
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 ..
>
>
>
>
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: markir@paradise.net.nz, mpuncia@census.gov.ph
Subject: Re: DB Design
In-Reply-To: <40AC7A3C.2050001@paradise.net.nz>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox