From: | Erik Jones <erik(at)myemma(dot)com> |
---|---|
To: | Enrico Sirola <enrico(dot)sirola(at)gmail(dot)com> |
Cc: | fdu(dot)xiaojf(at)gmail(dot)com, pgsql-general(at)postgresql(dot)org |
Subject: | Re: questions about very large table and partitioning |
Date: | 2008-02-18 17:42:59 |
Message-ID: | B74980F0-FF23-4461-A3E7-D2CFF5EAA096@myemma.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Feb 18, 2008, at 11:23 AM, Enrico Sirola wrote:
>
> Il giorno 18/feb/08, alle ore 17:37, fdu(dot)xiaojf(at)gmail(dot)com ha scritto:
>> 1) PostgreSQL only support partition by inheritance, and rules
>> have to
>> be created for each child table, this will result *a lot of* rules if
>> the number of child tables is large.
>>
>> Are there some smart ways to avoid this kind of mass ?
>
> you can obtain the same result using a trigger, but you must
> replace the trigger function every time you add/remove a partition.
This is not strictly true. If you use EXECUTE to run dynamically
built INSERT/UPDATE/DELETE statements you don't have to replace the
trigger each time.
Erik Jones
DBA | Emma®
erik(at)myemma(dot)com
800.595.4401 or 615.292.5888
615.292.0777 (fax)
Emma helps organizations everywhere communicate & market in style.
Visit us online at http://www.myemma.com
From | Date | Subject | |
---|---|---|---|
Next Message | Raymond O'Donnell | 2008-02-18 17:46:16 | Re: Auto incrementing primary keys |
Previous Message | Enrico Sirola | 2008-02-18 17:23:32 | Re: questions about very large table and partitioning |