Subject: Re: very large table
From: Simon Riggs <simon@2ndquadrant.com>
To: Praveen Raja <praveen.raja@netlight.se>
Cc: pgsql-performance@postgresql.org
In-Reply-To: <022801c565c4$6b1ac8c0$541510ac@sek.se>
References: <022801c565c4$6b1ac8c0$541510ac@sek.se>
Content-Type: text/plain; charset=UTF-8
Organization: 2nd Quadrant
Date: Wed, 01 Jun 2005 09:57:19 +0100
Message-Id: <1117616239.3844.898.camel@localhost.localdomain>
Mime-Version: 1.0
Content-Transfer-Encoding: quoted-printable

On Tue, 2005-05-31 at 11:37 +0200, Praveen Raja wrote:
> I=E2=80=99m trying to move an existing solution from MySQL to PostgreSQL.=
 As
> it is now the solution has 4 tables where data in inserted by an
> application. At regular intervals (10min) data from these tables is
> consolidated and moved to another table for reporting purposes. There
> exist many instances of these reporting tables and in total they are
> expected to hold about 500 million rows. There are about 200 of these
> reporting tables at the moment with data split among them. When a
> request comes in all these tables are searched.=20

> While moving to PostgreSQL is it a good idea to move from using
> multiple tables to one table for so many rows?=20

No. All of the same reasoning applies.=20

Try to keep each table small enough to fit easily in RAM.

Make sure you specify WITHOUT OIDS on the main data tables.

Best Regards, Simon Riggs