Re: table partitioning pl/pgsql helpers
От | Enrico Sirola |
---|---|
Тема | Re: table partitioning pl/pgsql helpers |
Дата | |
Msg-id | 703C285B-6BA9-4C4F-8A61-BABFEFDE5D5B@gmail.com обсуждение исходный текст |
Ответ на | Re: table partitioning pl/pgsql helpers (Robert Treat <robert@omniti.com>) |
Список | pgsql-general |
Hi Robert,
[...]
Il giorno 01/giu/07, alle ore 04:08, Robert Treat ha scritto:
We I set these up for our clients, I typically seperate the partition creationpiece from the data insertion piece. (Mostly as partition creation,especially with rules, is a table locking event, which is better done in anon-critical path). If you really must do it all in one go, you'll have a
I see, and now I agree with you it's better to decouple partition creation
and data insertion.
much better chance of accomplishing this using all triggers (and triggers arebetter anyway)... i think you could do it with a combination of rules and atrigger (on insert to parent, create new parition and insert into it anddelete from parent) but it would certainly need testing to make sure you donthave multi-rule evaluation... course since your making a trigger anyway...
Even more importantly, I just discovered (trying and then reading pgsql docs) that the rule
system is completely bypassed by the COPY FROM statement, so I think I'll rewrite
everything using some sort of trigger-generating procedure because I want this stuff
to work transparently (and we do lots of copy from).
Thanks for the advices,
Enrico Sirola
В списке pgsql-general по дате отправления: