pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Dmitry Ivanov <d.ivanov@postgrespro.ru>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Michael Paquier <michael.paquier@gmail.com>
Cc: Andres Freund <andres@anarazel.de>
Cc: Erik Rijkers <er@xs4all.nl>
Cc: Amit Langote <amitlangote09@gmail.com>
Cc: Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>
Cc: Rajkumar Raghuwanshi <rajkumar.raghuwanshi@enterprisedb.com>
Cc: Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>
Cc: Pg Hackers <pgsql-hackers@postgresql.org>
Cc: pgsql-hackers-owner@postgresql.org
Subject: Re: Declarative partitioning - another take
Date: Thu, 08 Dec 2016 19:13:44 +0300
Message-ID: <426b2b01-61e0-43aa-bd84-c6fcf516f1c3@postgrespro.ru> (raw)
In-Reply-To: <CA+TgmobTxn2+0x96h5Le+GOK5kw3J37SRveNfzEdx9s5-Yd8vA@mail.gmail.com>
References: <890ce68d-2cff-ccf3-67f7-6f5d3264dbfc@lab.ntt.co.jp>
	<CA+TgmobjAVgiXWqa3WmPO09Ma+o8c=3+JVYP+1fE_TFvNYJ5PQ@mail.gmail.com>
	<CA+HiwqE1-1w9GiPE3+oje00=y5mzTu8c8XCn=9jzKW4ik+3y9w@mail.gmail.com>
	<CA+Tgmob9o3+xgYHtGbfzUWm9bknRryx53Q5pEVFkzVHSDO=QXQ@mail.gmail.com>
	<78ae9888-7372-245d-cf6b-f655e6fe6c12@lab.ntt.co.jp>
	<ce3c665ba06aed715386e79ef2abc616@xs4all.nl>
	<CA+HiwqFJ2qyA7eWfu0XLE77zhN88jMeQTxBBD_J-Uw=7YWkG_A@mail.gmail.com>
	<CA+Tgmob==oNYLN2M-pVVaLNMZxqvXk3_EoUnJqqRdd-8tm0CNw@mail.gmail.com>
	<bf186a19e6b16d104b997e7c1698cb56@xs4all.nl>
	<CA+Tgmob6DJEQBd=qH2wZG1onYZ9R1Sji3q+GqCRUqQi+ug28Rw@mail.gmail.com>
	<20161208043942.ekjvyf7ddbxehh7c@alap3.anarazel.de>
	<CAB7nPqS1jYR5huoTAmCRWsjeYC=ap1qmonjM+rjKuHjqOzGaDg@mail.gmail.com>
	<CA+TgmobTxn2+0x96h5Le+GOK5kw3J37SRveNfzEdx9s5-Yd8vA@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>

Hi everyone,

> Of course, this is the beginning, not the end.  I've been thinking
> about next steps -- here's an expanded list:

> - more efficient plan-time partition pruning (constraint 
> exclusion is too slow)
> - run-time partition pruning
> - try to reduce lock levels
> ...

We (PostgresPro) have been working on pg_pathman for quite a while, and 
since it's obviously going to become the thing of the past, it would be a 
wasted effort if we didn't try to participate.

For starters, I'd love to work on both plan-time & run-time partition 
pruning. I created a custom node for run-time partition elimination, so I 
think I'm capable of developing something similar.


-- 
Dmitry Ivanov
Postgres Professional: http://www.postgrespro.com
Russian Postgres Company


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers



view thread (329+ messages)  latest in thread

Message-ID: <426b2b01-61e0-43aa-bd84-c6fcf516f1c3@postgrespro.ru>
Permalink:  ../426b2b01-61e0-43aa-bd84-c6fcf516f1c3@postgrespro.ru/
Also on:    postgresql.org/message-id/426b2b01-61e0-43aa-bd84-c6fcf516f1c3@postgrespro.ru

 · 

reply
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: d.ivanov@postgrespro.ru, robertmhaas@gmail.com, michael.paquier@gmail.com, andres@anarazel.de, er@xs4all.nl, amitlangote09@gmail.com, Langote_Amit_f8@lab.ntt.co.jp, rajkumar.raghuwanshi@enterprisedb.com, ashutosh.bapat@enterprisedb.com, pgsql-hackers-owner@postgresql.org
  Subject: Re: Declarative partitioning - another take
  In-Reply-To: <426b2b01-61e0-43aa-bd84-c6fcf516f1c3@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