Re:
От | Matt Casters |
---|---|
Тема | Re: |
Дата | |
Msg-id | 36073.212.100.172.237.1106311862.squirrel@212.100.172.237 обсуждение исходный текст |
Ответ на | Re: (Yann Michel <yann-postgresql@spline.de>) |
Список | pgsql-performance |
>> > Some people have been doing it using a union view. There isn't actually >> > a partition feature. >> >> Actually, there is. If found this example on pgsql-performance: >> >> >> CREATE TABLE super_foo ( partition NUMERIC, bar NUMERIC ); >> >> ANALYZE super_foo ; >> >> >> >> CREATE TABLE sub_foo1 () INHERITS ( super_foo ); > [...] >> >> >> >> CREATE TABLE sub_foo2 () INHERITS ( super_foo ); > [...] >> >> > > Yes, this could be used instead of a view. But there is one thing > missing. You can't just insert into super_foo and aquire the "correct > partition". You will still have to insert into the correct underlying > table. "Real" partitioning will take care of correct partition > selection. This IS bad news. It would mean a serious change in the ETL. I think I can solve the other problems, but I don't know about this one... Regards, Matt
В списке pgsql-performance по дате отправления: