Em 30-09-2011 14:01, Merlin Moncure escreveu:
2011/9/29 Ondrej Ivanič<ondrej.iva...@gmail.com>:
Hi,
On 30 September 2011 01:08, Kevin Grittner<kevin.gritt...@wicourts.gov> wrote:
Is there a suggested number of child tables for table
partitioning,
Generally, don't go over about 100 partitions per table.
Having 365 partitions per table is fine...
yeah -- the system was certainly designed to support 'dozens to
hundreds', but 'hundreds of thousands' is simply not realistic. any
measurable benefit gained from partitioning is going to be var
exceeded by the database having to track so many tables.
btw, partitioning for purposes of performance is a dubious strategy
unless you can leverage non-uniform access patterns of the data or do
other tricks that allow simplification of structures (like removing
'company_id' from all tables and indexes because it's implied by the
partition itself).
merlin
Can we see the transparent table partitioningimplemented in Postgres 9.2
version before the end of the world in 2012? ;)
Today, it is very difficult to maintain table partitioning schemes even
with small number of partitions.
Anyway, congrats for the superb 9.1 version!
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
