| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> |
| Cc: | Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: expanding inheritance in partition bound order |
| Date: | 2017-08-17 02:22:13 |
| Message-ID: | CA+TgmoZ_B-QSV0EW8dYOm+Rmu=xH0RTKmdDHN4uUtRpNWefwUQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Aug 16, 2017 at 10:12 PM, Amit Langote
<Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Noah Misch | 2017-08-17 02:24:41 | Re: One-shot expanded output in psql using \gx |
| Previous Message | Amit Langote | 2017-08-17 02:12:56 | Re: expanding inheritance in partition bound order |