| From: | Rod Taylor <rbt(at)rbt(dot)ca> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | Richard Huxton <dev(at)archonet(dot)com>, Girish Bajaj <gbajaj(at)tietronix(dot)com>, pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: Table Partitioning and Rules |
| Date: | 2003-07-17 19:22:06 |
| Message-ID: | 1058469725.97321.86.camel@jester |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
On Thu, 2003-07-17 at 19:03, Josh Berkus wrote:
> 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.
PostgreSQL will go well beyond 2 billion rows in a table. It just
becomes difficult to use OIDs.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Girish Bajaj | 2003-07-17 19:22:41 | Re: Table Partitioning and Rules |
| Previous Message | Scott Cain | 2003-07-17 19:18:25 | Re: OR vs UNION |