| From: | "Praveen Raja" <praveen(dot)raja(at)netlight(dot)se> |
|---|---|
| To: | <pgsql-performance(at)postgresql(dot)org> |
| Subject: | very large table |
| Date: | 2005-05-31 09:37:48 |
| Message-ID: | 022801c565c4$6b1ac8c0$541510ac@sek.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Hi
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?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dirk Lutzebäck | 2005-05-31 13:16:37 | SURVEY: who is running postgresql on 8 or more CPUs? |
| Previous Message | Tobias Brox | 2005-05-31 05:59:32 | Re: Index on a NULL-value |