Re: Declarative partitioning - another take

Amit Langote <langote_amit_f8@lab.ntt.co.jp>

From: Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>

To: "Tsunakawa, Takayuki" <tsunakawa.takay@jp.fujitsu.com>, "'Alexander Korotkov'" <a.korotkov@postgrespro.ru>, Robert Haas <robertmhaas@gmail.com>

Cc: Dmitry Ivanov <d.ivanov@postgrespro.ru>, Michael Paquier <michael.paquier@gmail.com>, Andres Freund <andres@anarazel.de>, Erik Rijkers <er@xs4all.nl>, Amit Langote <amitlangote09@gmail.com>, Rajkumar Raghuwanshi <rajkumar.raghuwanshi@enterprisedb.com>, Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>, Pg Hackers <pgsql-hackers@postgresql.org>, "pgsql-hackers-owner@postgresql.org" <pgsql-hackers-owner@postgresql.org>

Date: 2016-12-09T01:19:46Z

Lists: pgsql-hackers

On 2016/12/09 10:09, Tsunakawa, Takayuki wrote:
> Another requirement was subpartitioning.  Will this be possible with the current infrastructure, or does this need drastic change?

It does support sub-partitioning, although the syntax is a bit different.

Thanks,
Amit

Commits

Fix typo.
- 03bf59676ea0 10.0 landed
Document trigger-firing behavior for inheritance/partitioning.
- e17628145ac3 10.0 landed
Fire per-statement triggers on partitioned tables.
- e180c8aa8caf 10.0 landed
Set ecxt_scantuple correctly for tuple routing.
- 132488bfee68 10.0 landed
Fix interaction of partitioned tables with BulkInsertState.
- b1ecb9b3fcfb 10.0 landed
Avoid core dump for empty prepared statement in an aborted transaction.
- ba61a04bc7fe 10.0 cited
Fix some problems in check_new_partition_bound().
- 8a8afe2f54c2 10.0 landed
Remove unnecessary arguments from partitioning functions.
- 18fc5192a631 10.0 cited
Fix reporting of constraint violations for table partitioning.
- f1b4c771ea74 10.0 cited
Fix tuple routing in cases where tuple descriptors don't match.
- 2ac3ef7a01df 10.0 cited
Invalid parent's relcache after CREATE TABLE .. PARTITION OF.
- 7cd0fd655d68 10.0 landed
Doc: improve documentation about inheritance.
- 162477a63d3c 10.0 cited