From: Rod Taylor <rbt@rbt.ca>
To: Josh Berkus <josh@agliodbs.com>
Cc: Richard Huxton <dev@archonet.com>
Cc: Girish Bajaj <gbajaj@tietronix.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: Table Partitioning and Rules
Date: 17 Jul 2003 19:22:06 +0000
Message-ID: <1058469725.97321.86.camel@jester> (raw)
In-Reply-To: <200307171203.13134.josh@agliodbs.com>
References: <002f01c34c87$a72f59a0$7764a8c0@tietronix.com>
<200307171952.07485.dev@archonet.com>
<200307171203.13134.josh@agliodbs.com>
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.
Attachments:
signature.asc (application/pgp-signature, 186B) download
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-sql@postgresql.org
Cc: rbt@rbt.ca, josh@agliodbs.com, dev@archonet.com, gbajaj@tietronix.com
Subject: Re: Table Partitioning and Rules
In-Reply-To: <1058469725.97321.86.camel@jester>
* 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