Re: Declarative partitioning - another take
От | Amit Langote |
---|---|
Тема | Re: Declarative partitioning - another take |
Дата | |
Msg-id | b6518801-3d0a-0de4-d00b-a1a494deda8b@lab.ntt.co.jp обсуждение исходный текст |
Ответ на | Re: Declarative partitioning - another take (Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>) |
Список | pgsql-hackers |
On 2016/11/11 20:49, Ashutosh Bapat wrote: > I have not looked at the latest set of patches, but in the version > that I have we create one composite type for every partition. This > means that if there are thousand partitions, there will be thousand > identical entries in pg_type. Since all the partitions share the same > definition (by syntax), it doesn't make sense to add so many identical > entries. Moreover, in set_append_rel_size(), while translating the > expressions from parent to child, we add a ConvertRowtypeExpr instead > of whole-row reference if reltype of the parent and child do not match > (adjust_appendrel_attrs_mutator()) > if (appinfo->parent_reltype != appinfo->child_reltype) > { > ConvertRowtypeExpr *r = makeNode(ConvertRowtypeExpr); > > I guess, we should set reltype of child to that of parent for > declarative partitions. Thanks for the suggestion. I agree that partitions having the same reltype as the parent will help a number of cases including the one you mentioned, but I haven't yet considered how invasive such a change will be. Thanks, Amit
В списке pgsql-hackers по дате отправления: