From: Jaime Casanova <jcasanov@systemguards.com.ec>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Gregory Stark <stark@enterprisedb.com>
Cc: Alvaro Herrera <alvherre@commandprompt.com>
Cc: Nikhil Sontakke <nikhil.sontakke@enterprisedb.com>
Cc: Emmanuel Cecchet <manu@frogthinker.org>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: Fwd: [PATCHES] Auto Partitioning Patch - WIP version 1
Date: Thu, 27 Nov 2008 10:12:13 -0500
Message-ID: <3073cc9b0811270712l6384c28awac4f0318c704df99@mail.gmail.com> (raw)
In-Reply-To: <3073cc9b0811270710p3a2e5ae9s10f66b529550c03e@mail.gmail.com>
References: <3073cc9b0810220744y987173avd560a33fcb58ede5@mail.gmail.com>
<603c8f070811261352ta6da0b8xcbb8aaf87f050e6e@mail.gmail.com>
<3073cc9b0811261613l18e5283ft448ea74fed414dd@mail.gmail.com>
<603c8f070811262009v459d0701w151c16533d4ab947@mail.gmail.com>
<a301bfd90811270106k39d60318s7fc871a477a2b58d@mail.gmail.com>
<20081127120402.GC4586@alvh.no-ip.org>
<603c8f070811270507i36e18e0bu5d461a4f957e24d3@mail.gmail.com>
<871vwxpa7b.fsf@oxford.xeocode.com>
<603c8f070811270641u55bbf340p3383dcc6a6f1f6e8@mail.gmail.com>
<3073cc9b0811270710p3a2e5ae9s10f66b529550c03e@mail.gmail.com>
On Thu, Nov 27, 2008 at 10:10 AM, Jaime Casanova
<jcasanov@systemguards.com.ec> wrote:
> On Thu, Nov 27, 2008 at 9:41 AM, Robert Haas <robertmhaas@gmail.com> wrote:
>> On Thu, Nov 27, 2008 at 8:31 AM, Gregory Stark <stark@enterprisedb.com> wrote:
>>>> CREATE PARTITION transaction_2008_11 ON transaction WHERE record_date
>>>> BETWEEN '2008-11-01' AND '2008-11-30';
>>>
>>> I think the main advantage to a better partitioning method would be teaching
>>> Postgres about the partition key. Instead of a collection of different
>>> constraints Postgres would know that "record_date" is *always* the partition
>>> key. So it wouldn't have to be specified every time you declare a partition.
>>
>> Hmm... I thought the main advantage would be that you wouldn't have
>> to manually add constraints to all of the child tables, and you
>> wouldn't have to manually add rules/triggers to the parent table to
>> redirect DML operations.
>>
>
> ok. what about let CREATE TABLE WITH PARTITIONING to create an entry
> in a catalog indicating the key of the partition and install the
> triggers and let the trigger decide if it has the partition to insert
> the new row (making UPDATE working almost as DELETE+INSERT if it needs
> to change of partitions) or create the new partition maybe with an
> apropiate CREATE PARTITION...
>
i thik i have to clarify this...
i intend to say that, the trigger will insert or create the partition
and insert...
--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
AsesorÃa y desarrollo de sistemas
Guayaquil - Ecuador
Cel. +59387171157
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-patches@postgresql.org
Cc: jcasanov@systemguards.com.ec, robertmhaas@gmail.com, stark@enterprisedb.com, alvherre@commandprompt.com, nikhil.sontakke@enterprisedb.com, manu@frogthinker.org, pgsql-hackers@postgresql.org
Subject: Re: Fwd: [PATCHES] Auto Partitioning Patch - WIP version 1
In-Reply-To: <3073cc9b0811270712l6384c28awac4f0318c704df99@mail.gmail.com>
* 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