Skip site navigation (1) Skip section navigation (2)

table partioning performance

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 (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-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.

Responses

pgsql-performance by date

Next:From: Joshua D. DrakeDate: 2007-01-07 04:56:47
Subject: Re: High update activity, PostgreSQL vs BigDBMS
Previous:From: Guy RouillierDate: 2007-01-07 04:32:59
Subject: Re: High update activity, PostgreSQL vs BigDBMS

pgsql-hackers by date

Next:From: Tom LaneDate: 2007-01-07 04:38:53
Subject: Re: SGML index build fix
Previous:From: Bruce MomjianDate: 2007-01-07 04:28:23
Subject: SGML index build fix

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group