From: | Michael Paesold <mpaesold(at)gmx(dot)at> |
---|---|
To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
Cc: | NikhilS <nikkhils(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, David Fetter <david(at)fetter(dot)org>, "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com>, PostgreSQL Docs <pgsql-docs(at)postgresql(dot)org>, PostgreSQL Patches <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: [DOCS] Partition: use triggers instead of rules |
Date: | 2007-11-29 16:06:29 |
Message-ID: | 474EE385.9030103@gmx.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs pgsql-patches |
Joshua D. Drake wrote:
> Michael Paesold wrote:
>> I would also add another sentence about *why* the recommendation was
>> changed. We have one rule-based setup here, and it has been working
>> flawlessly for us,... so personally I don't even know the reasons.
>>
>
> Rules are extremely slow in comparisons and not anywhere near as
> flexible. As I said up post yesterday... they work well in the basic
> partitioning configuration but anything else they are extremely deficient.
Ah, thanks for that summary. How do they compare to triggers dynamically
EXECUTEing the inserts? Is that a better solution, or should one really
just use the IF ... ELSIF ... ELSIF ... ELSE pattern as suggested in the
new docs? (Which means one has to re-create the complete trigger each
time a partition is added.)
Best Regards
Michael Paesold
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-11-29 16:17:25 | Re: [PATCHES] Partition: use triggers instead of rules |
Previous Message | Joshua D. Drake | 2007-11-29 16:01:34 | Re: [PATCHES] Partition: use triggers instead of rules |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-11-29 16:17:25 | Re: [PATCHES] Partition: use triggers instead of rules |
Previous Message | Joshua D. Drake | 2007-11-29 16:01:34 | Re: [PATCHES] Partition: use triggers instead of rules |