| From: | Vincenzo Romano <vincenzo(dot)romano(at)notorand(dot)it> |
|---|---|
| To: | Dimitri Fontaine <dfontaine(at)hi-media(dot)com> |
| Cc: | David Fetter <david(at)fetter(dot)org>, Sam Jas <samjas33(at)yahoo(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Table Partitioning Advice Request |
| Date: | 2009-12-17 15:41:41 |
| Message-ID: | 3eff28920912170741y5baf71b4s4ae89bf64cb228e0@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
2009/12/17 Dimitri Fontaine <dfontaine(at)hi-media(dot)com>:
> Vincenzo Romano <vincenzo(dot)romano(at)notorand(dot)it> writes:
>> Is there any performance study for the trigger-based implementation?
>
> Consider that if you use RULE to partition, when you DROP a partition
> the INSERTs are locked out because the query depends on the table being
> droped.
>
> That alone could lead you to stop considering RULEs for partitioning.
In that case I would also drop the relevant rule(s).
But it seems anyway that the rule system would need to scan all the
rules in order to know which one(s) to apply.
And, at least in my case, I would have hundreds of rules ...
Thanks for the hint, anyway.
--
Vincenzo Romano
NON QVIETIS MARIBVS NAVTA PERITVS
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gauthier, Dave | 2009-12-17 15:55:57 | Re: Justifying a PG over MySQL approach to a project |
| Previous Message | Adrian Klaver | 2009-12-17 15:38:57 | Re: Automatic truncation of character values & casting to the type of a column type |