Re: [HACKERS] [Proposal] Make the optimiser aware of partitions ordering - Mailing list pgsql-hackers

From Robert Haas
Subject Re: [HACKERS] [Proposal] Make the optimiser aware of partitions ordering
Date
Msg-id CA+TgmoY4ifAaf6c6G6ytc_uTBvAkuNa_Aru0HNp-eSA7PA66Dg@mail.gmail.com
Whole thread Raw
In response to [HACKERS] [Proposal] Make the optimiser aware of partitions ordering  (Ronan Dunklau <ronan.dunklau@dalibo.com>)
Responses Re: [HACKERS] [Proposal] Make the optimiser aware of partitions ordering  (Ronan Dunklau <ronan.dunklau@dalibo.com>)
List pgsql-hackers
On Mon, Mar 20, 2017 at 6:31 AM, Ronan Dunklau <ronan.dunklau@dalibo.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.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: [HACKERS] Inadequate traces in TAP tests
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] Re: [COMMITTERS] pgsql: Improve pg_dump regression tests and code coverage