Re: [HACKERS] Partition-wise join for join between (declaratively)partitioned tables
От | Amit Langote |
---|---|
Тема | Re: [HACKERS] Partition-wise join for join between (declaratively)partitioned tables |
Дата | |
Msg-id | 394b7b44-1c84-d917-2d8a-05bf767233ef@lab.ntt.co.jp обсуждение исходный текст |
Ответ на | Re: [HACKERS] Partition-wise join for join between (declaratively)partitioned tables (Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>) |
Ответы |
Re: Partition-wise join for join between (declaratively)partitioned tables
|
Список | pgsql-hackers |
Hi Ashutosh, On 2017/03/23 21:48, Ashutosh Bapat wrote: >>> I have fixed all the issues reported till now. I've tried to fix your 0012 patch (Multi-level partitioned table expansion) considering your message earlier on this thread [1]. Especially the fact that no AppendRelInfo and RelOptInfo are allocated for partitioned child tables as of commit d3cc37f1d [2]. I've fixed expand_inherited_rtentry() such that AppendRelInfo *is* allocated for a partitioned child RTEs whose rte->inh is set to true. Such an RTE is recursively expanded with that RTE the parent. Also as I mentioned elsewhere [3], the multi-level inheritance expansion of partitioned table will break update/delete for partitioned table, which is because inheritance_planner() is not ready to handle inheritance sets structured that way. I tried to refactor inheritance_planner() such that its core logic can be recursively invoked for partitioned child RTEs. The resulting child paths and other auxiliary information related to planning across the hierarchy are maintained in one place using a struct to hold the same in a few flat lists. The refactoring didn't break any existing tests and a couple of new tests are added to check that it indeed works for multi-level partitioned tables expanded using new multi-level structure. There is some test failure in 0014 (Multi-level partition-wise join tests), probably because of the changes I made to 0012, which I didn't get time to check why, although I've checked using an example that multi-level join planning still works, so it's not completely broken either. Thanks, Amit [1] https://www.postgresql.org/message-id/CAFjFpRefs5ZMnxQ2vP9v5zOtWtNPuiMYc01sb1SWjCOB1CT%3DuQ%40mail.gmail.com [2] https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=d3cc37f1d [3] https://www.postgresql.org/message-id/744d20fe-fc7b-f89e-8d06-6496ec537b86%40lab.ntt.co.jp -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Вложения
В списке pgsql-hackers по дате отправления: