Postgres Pro
Downloads
Home   >   mailing lists

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

From Robert Haas
Subject Re: [HACKERS] expanding inheritance in partition bound order
Date
Msg-id CA+TgmoZ_B-QSV0EW8dYOm+Rmu=xH0RTKmdDHN4uUtRpNWefwUQ@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] expanding inheritance in partition bound order  (Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>)
Responses Re: [HACKERS] expanding inheritance in partition bound order  (Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>)
List pgsql-hackers
Tree view 
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.

> There are a bunch of callers of find_all_inheritors() and
> find_inheritance_children.  Changes to make them all declare a pointless
> variable seemed off to me.  The conditional in question doesn't seem to be
> that expensive.

+1.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

pgsql-hackers by date:

Previous
From: Amit Langote
Date:
Subject: Re: [HACKERS] expanding inheritance in partition bound order
Next
From: Noah Misch
Date:
Subject: Re: [HACKERS] One-shot expanded output in psql using \gx