From: Rick Schumeyer <rschumeyer@ieee.org>
To: pgsql-performance@postgresql.org
Subject: table partitioning: effects of many sub-tables (was COPY too slow...)
Date: Tue, 6 Dec 2005 22:06:52 -0500
Message-ID: <000101c5fadb$470c7df0$0200a8c0@dell8200> (raw)
Based on a suggestion on the postgis list, I partitioned my 80 million (for
now) record table into
subtables of about 230k records (the amount of data collected in five
minutes). At the moment
I have 350 subtables.
Everything seems to be great.COPY time is ok, building a geometric index on
"only" 230k records
is ok, query performance is ok.
I'm a little concerned about having so many subtables. 350 tables is not
bad, but what happens if
the number of subtables grows into the thousands? Is there a practical
limit to the effectiveness
partitioning?
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: rschumeyer@ieee.org
Subject: Re: table partitioning: effects of many sub-tables (was COPY too slow...)
In-Reply-To: <000101c5fadb$470c7df0$0200a8c0@dell8200>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox