Re: Table Partitioning and Rules

Girish,

> > Essentially Im trying to store a persons information in a table in the
> > database. Since we could have millions of people, with duplicates! Ive
> > decided we need to partition the table into segments where all people with
> > the LastName starting from A to G will be in one table. H-N will be in
> > another table and O-Z in the third. Ive created a VIEW that does a UNION
on
> > all the tables.

This sounds hideously inefficient and a management headache besides. I think
PostgreSQL will accept up to 2 billion rows in any one table, and splitting
stuff into 3 tables will not improve your performance ... quite the opposite.

Change your database design.

--
-Josh Berkus
Aglio Database Solutions
San Francisco