From: | "Colin Taylor" <colin(dot)taylor(at)gmail(dot)com> |
---|---|
To: | pgsql-performance(at)postgresql(dot)org |
Subject: | table partioning performance |
Date: | 2007-01-07 04:37:08 |
Message-ID: | 84d3067d0701062037k3229c9ddjbde73b1fd79ee209@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-performance |
Hi there, we've partioned a table (using 8.2) by day due to the 50TB of
data (500k row size, 100G rows) we expect to store it in a year.
Our performance on inserts and selects against the master table is
disappointing, 10x slower (with ony 1 partition constraint) than we get by
going to the partioned table directly. Browsing the list I get the
impression this just a case of too many partitions? would be better off
doing partitions of partitions ?
Any other advice or pointers to more information with dealing with these
sorts of scales appreciated.
thanks
Colin.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-01-07 04:38:53 | Re: SGML index build fix |
Previous Message | Bruce Momjian | 2007-01-07 04:28:23 | SGML index build fix |
From | Date | Subject | |
---|---|---|---|
Next Message | Joshua D. Drake | 2007-01-07 04:56:47 | Re: High update activity, PostgreSQL vs BigDBMS |
Previous Message | Guy Rouillier | 2007-01-07 04:32:59 | Re: High update activity, PostgreSQL vs BigDBMS |