| From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | Praveen Raja <praveen(dot)raja(at)netlight(dot)se> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: very large table |
| Date: | 2005-06-01 08:57:19 |
| Message-ID: | 1117616239.3844.898.camel@localhost.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Tue, 2005-05-31 at 11:37 +0200, Praveen Raja wrote:
> I’m 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.
> While moving to PostgreSQL is it a good idea to move from using
> multiple tables to one table for so many rows?
No. All of the same reasoning applies.
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2005-06-01 09:06:19 | Re: slow queries, possibly disk io |
| Previous Message | Martin Fandel | 2005-06-01 08:50:31 | Re: postgresql-8.0.1 performance tuning |