From: | Ronan Dunklau <ronan(dot)dunklau(at)dalibo(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | pgsql-hackers Hackers <pgsql-hackers(at)postgresql(dot)org>, Julien Rouhaud <julien(dot)rouhaud(at)dalibo(dot)com> |
Subject: | Re: [Proposal] Make the optimiser aware of partitions ordering |
Date: | 2017-03-20 15:03:45 |
Message-ID: | 2701654.FqDTblohPo@ronan_laptop |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On lundi 20 mars 2017 15:52:03 CET Robert Haas wrote:
> On Mon, Mar 20, 2017 at 6:31 AM, Ronan Dunklau <ronan(dot)dunklau(at)dalibo(dot)com>
wrote:
> > With range partitioning, we guarantee that each partition contains non-
> > overlapping values. Since we know the range allowed for each partition, it
> > is possible to sort them according to the partition key (as is done
> > already for looking up partitions).
> >
> > Thus, we ca generate sorted Append plans instead of MergeAppend when
> > sorting occurs on the partition key.
>
> Great idea. This is too late for v10 at this point, but please add it
> to the next CommitFest so we don't forget about it.
I know it is too late, and thought that it was too early to add it to the
commitfest properly since so many design decisions should be discussed. Thanks
for the feedback, I added it.
--
Ronan Dunklau
http://dalibo.com - http://dalibo.org
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2017-03-20 15:06:09 | Re: Re: [COMMITTERS] pgsql: Improve pg_dump regression tests and code coverage |
Previous Message | Pavan Deolasee | 2017-03-20 15:03:23 | Re: Patch: Write Amplification Reduction Method (WARM) |