From: Ildar Musin <i.musin@postgrespro.ru>
To: pgsql-hackers@postgresql.org
Subject: Re: Declarative partitioning
Date: Mon, 29 Feb 2016 03:14:55 +0500
Message-ID: <56D3715F.1060102@postgrespro.ru> (raw)
In-Reply-To: <56C28D8A.2060608@lab.ntt.co.jp>
References: <55D3093C.5010800@lab.ntt.co.jp>
<56A23484.4000504@2ndquadrant.com>
<56A9D51E.2000508@lab.ntt.co.jp>
<56C1302D.6070403@lab.ntt.co.jp>
<CADkLM=cLntJWEzCjW1LUbnRAYz6+-ZooO0FXKg+7rdkTaVE+2g@mail.gmail.com>
<56C26D27.40108@lab.ntt.co.jp>
<WM!d6dd475995a24385f07585c1088a8d539ae7cd66bc94bda3302a62148d440ab7c4acfd99eb4215a796034bfbac104bbd!@asav-2.01.com>
<56C28C4C.5090409@agliodbs.com>
<56C28D8A.2060608@lab.ntt.co.jp>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
16/02/16 07:46, Amit Langote wrote:
> Hi Josh,
>
> On 2016/02/16 11:41, Josh berkus wrote:
>> On 02/15/2016 04:28 PM, Amit Langote wrote:
>>> Also, you won't see any optimizer and executor changes. Queries will still
>>> use the same plans as existing inheritance-based partitioned tables,
>>> although as I mentioned, constraint exclusion won't yet kick in. That will
>>> be fixed very shortly.
>> We're not going to use CE for the new partitioning long-term, are we? This
>> is just the first version, right?
> Yes. My approach in previous versions of stuffing major planner changes in
> with the syntax patch was not quite proper in retrospect. So, I thought
> I'd propose any major planner (and executor) changes later.
>
> Thanks,
> Amit
>
Hello Amit,
Thank you for your work. I'm currently working on extension aimed at
planner optimization for partitioned tables
(https://github.com/postgrespro/pg_pathman). At this moment I have an
implementation of binary search for range partitioned tables with basic
partitioning keys (date, timestamp, integers etc). And I'd like to try
to combine your syntax and infrastructure with my binary search
implementation.
There likely will be changes in range syntax and partitions cache
structure based on discussion. So looking forward for your next patch.
Ildar
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: i.musin@postgrespro.ru
Subject: Re: Declarative partitioning
In-Reply-To: <56D3715F.1060102@postgrespro.ru>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox