From: | alexandre - aldeia digital <adaldeia(at)gmail(dot)com> |
---|---|
To: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: the number of child tables --table partitioning |
Date: | 2011-09-30 17:13:37 |
Message-ID: | 4E85F8C1.3040900@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Em 30-09-2011 14:01, Merlin Moncure escreveu:
> 2011/9/29 Ondrej Ivanič<ondrej(dot)ivanic(at)gmail(dot)com>:
>> Hi,
>>
>> On 30 September 2011 01:08, Kevin Grittner<Kevin(dot)Grittner(at)wicourts(dot)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!
From | Date | Subject | |
---|---|---|---|
Next Message | bricklen | 2011-09-30 18:07:54 | Re: array_except -- Find elements that are not common to both arrays |
Previous Message | Merlin Moncure | 2011-09-30 17:01:27 | Re: the number of child tables --table partitioning |