Re: Remove mention in docs that foreign keys on partitioned tablesare not supported - Mailing list pgsql-hackers

From Tomas Vondra
Subject Re: Remove mention in docs that foreign keys on partitioned tablesare not supported
Date
Msg-id ff9d5219-cf84-ea2a-e841-d26b625cab3f@2ndquadrant.com
Whole thread Raw
In response to Re: Remove mention in docs that foreign keys on partitioned tablesare not supported  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Remove mention in docs that foreign keys on partitioned tablesare not supported
List pgsql-hackers

On 06/29/2018 02:30 PM, Robert Haas wrote:
> On Wed, Jun 27, 2018 at 10:26 PM, Amit Langote
> <Langote_Amit_f8@lab.ntt.co.jp> wrote:
>> By the way, picking up on the word "inherited" in the error message shown
>> above, I wonder if you decided against using similar terminology
>> intentionally.
> 
> Good question.
> 
>> I guess the thinking there is that the terminology being
>> used extensively with columns and constraints ("inherited column/check
>> constraint cannot be dropped", etc.) is just a legacy of partitioning
>> sharing implementation with inheritance.
> 
> It seems to me that we can talk about things being inherited by
> partitions even if we're calling the feature partitioning, rather than
> inheritance.  Maybe that's confusing, but then again, maybe it's not
> that confusing.
> 

my 2c: I don't think it's confusing. Inheritance is a generic concept, 
not attached exclusively to the "table inheritance". If you look at docs 
from other databases, you'll see "partition inherits" all the time.

regards

-- 
Tomas Vondra                  http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


pgsql-hackers by date:

Previous
From: Etsuro Fujita
Date:
Subject: Re: Expression errors with "FOR UPDATE" and postgres_fdw with partitionwise join enabled.
Next
From: Tomas Vondra
Date:
Subject: Re: POC: GROUP BY optimization