Postgres Pro
Downloads
Home   >   mailing lists

Re: [HACKERS] expanding inheritance in partition bound order - Mailing list pgsql-hackers

From Amit Langote
Subject Re: [HACKERS] expanding inheritance in partition bound order
Date
Msg-id 1e891c0d-8c40-1410-81f8-229778af495a@lab.ntt.co.jp
Whole thread Raw
In response to Re: [HACKERS] expanding inheritance in partition bound order  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: [HACKERS] expanding inheritance in partition bound order  (Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>)
List pgsql-hackers
Tree view 
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.

Thanks,
Amit

pgsql-hackers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: [HACKERS] One-shot expanded output in psql using \gx
Next
From: Michael Paquier
Date:
Subject: Re: [HACKERS] SCRAM salt length