Subject: Re: Table Partitioning and Rules
From: Rod Taylor <rbt@rbt.ca>
To: Josh Berkus <josh@agliodbs.com>
Cc: Richard Huxton <dev@archonet.com>,
	Girish Bajaj <gbajaj@tietronix.com>, pgsql-sql@postgresql.org
In-Reply-To: <200307171203.13134.josh@agliodbs.com>
References: <002f01c34c87$a72f59a0$7764a8c0@tietronix.com>
	<200307171952.07485.dev@archonet.com>
	<200307171203.13134.josh@agliodbs.com>
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="=-f9WFjJSPPKllRmCdnXft"
Message-Id: <1058469725.97321.86.camel@jester>
Mime-Version: 1.0
Date: 17 Jul 2003 19:22:06 +0000

--=-f9WFjJSPPKllRmCdnXft
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Thu, 2003-07-17 at 19:03, Josh Berkus wrote:
> Girish,
>=20
> > > 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 UN=
ION=20
> on
> > > all the tables.
>=20
> This sounds hideously inefficient and a management headache besides.  I t=
hink=20
> PostgreSQL will accept up to 2 billion rows in any one table, and splitti=
ng=20
> stuff into 3 tables will not improve your performance ... quite the oppos=
ite.

PostgreSQL will go well beyond 2 billion rows in a table.  It just
becomes difficult to use OIDs.

--=-f9WFjJSPPKllRmCdnXft
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (FreeBSD)

iD8DBQA/Fvdd6DETLow6vwwRAp6lAJ94T/+JVoy4PRj6FoXPKtVsltxO1wCdE+Al
mTRNGiAwHXzj3bO1YAzTZD0=
=hgHJ
-----END PGP SIGNATURE-----

--=-f9WFjJSPPKllRmCdnXft--