Re: expanding inheritance in partition bound order
Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>
From: Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>
To: Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>
Cc: Robert Haas <robertmhaas@gmail.com>,
Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2017-08-17T04:56:53Z
Lists: pgsql-hackers
On Thu, Aug 17, 2017 at 8:06 AM, Amit Langote <Langote_Amit_f8@lab.ntt.co.jp> wrote: > On 2017/08/17 11:22, Robert Haas wrote: >> On Wed, Aug 16, 2017 at 10:12 PM, Amit Langote >> <Langote_Amit_f8@lab.ntt.co.jp> wrote: >>>> In the catalogs we are using full "partitioned" e.g. pg_partitioned_table. May >>>> be we should name the column as "inhchildpartitioned". >>> >>> Sure. >> >> I suggest inhpartitioned or inhispartition. inhchildpartitioned seems too long. > > inhchildpartitioned indeed seems long. > > Since we storing if the child table (one with the OID inhrelid) is > partitioned, inhpartitioned seems best to me. Will implement that. inhchildpartitioned is long but clearly tells that the child table is partitioned, not the parent. pg_inherit can have parents which are not partitioned, so it's better to have self-explanatory catalog name. I am fine with some other name as long as it's clear. -- Best Wishes, Ashutosh Bapat EnterpriseDB Corporation The Postgres Database Company
Commits
-
Make RelationGetPartitionDispatchInfo expand depth-first.
- 77b6b5e9ceca 11.0 landed
-
Expand partitioned tables in PartDesc order.
- 30833ba154e0 11.0 landed
-
Don't lock tables in RelationGetPartitionDispatchInfo.
- 7c0ca2900f7c 10.0 landed
- 54cde0c4c058 11.0 landed
-
Speed up dropping tables with many partitions.
- c1e0e7e1d790 10.0 cited