Re: [HACKERS] [Proposal] Make the optimiser aware of partitions ordering
| От | Julien Rouhaud |
|---|---|
| Тема | Re: [HACKERS] [Proposal] Make the optimiser aware of partitions ordering |
| Дата | |
| Msg-id | CAOBaU_Y5OKa1xmHi2+quucxMAP=rV1UYfVpF+XWiepPwdhaQQA@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: [HACKERS] [Proposal] Make the optimiser aware of partitions ordering (Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>) |
| Ответы |
Re: [HACKERS] [Proposal] Make the optimiser aware of partitions ordering
|
| Список | pgsql-hackers |
On Thu, Sep 21, 2017 at 10:52 AM, Ashutosh Bapat <ashutosh.bapat@enterprisedb.com> wrote: > With 9140cf8269b0c4ae002b2748d93979d535891311, we store the > RelOptInfos of partitions in the RelOptInfo of partitioned table. For > range partitioned table without default partition, they are arranged > in the ascending order of partition bounds. This patch may avoid > MergeAppend if the sort keys match partition keys by creating an > Append path by picking sorted paths from partition RelOptInfos in > order. You may use slightly modified version of > add_paths_to_append_rel(). Yes, I just saw this commit this morning, and this is exactly what I was missing, thanks for the pointer and the patch! -- 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 по дате отправления: