Re: [HACKERS] New partitioning - some feedback - Mailing list pgsql-hackers

From Ashutosh Bapat
Subject Re: [HACKERS] New partitioning - some feedback
Date
Msg-id CAFjFpReNpUiuh-XPyqDZG2CWr5TcZ1VayqVuvYBGp-=6OM5S0g@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] New partitioning - some feedback  (Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>)
Responses Re: [HACKERS] New partitioning - some feedback
List pgsql-hackers
On Wed, Jul 12, 2017 at 8:23 AM, Amit Langote
<Langote_Amit_f8@lab.ntt.co.jp> wrote:
> On 2017/07/11 18:57, Ashutosh Bapat wrote:
>> On Tue, Jul 11, 2017 at 4:16 AM, David Fetter <david@fetter.org> wrote:
>>> So whatever we land on needs to mention partition_of and
>>> has_partitions.  Is that latter just its immediate partitions?
>>> Recursion all the way down?  Somewhere in between?
>>>
>>
>> We have patches proposed to address some of those concerns at [1]
>>
>> [1] https://www.postgresql.org/message-id/CAFjFpRcs5fOSfaAGAjT5C6=YvDD7MRx3knf_SpB5DQZOJgjerA@mail.gmail.com
>
> ISTM, David is talking about the "list tables" (bare \d without any
> pattern) case.  That is, listing partitioned tables as of type
> "partitioned table" instead of "table" as we currently do.  The linked
> patch, OTOH, is for "describe table" (\d <object_name_pattern>) case.

Right, the patches don't exactly do what David is suggesting, but
those I believe have code to annotate the tables with "has partitions"
and also the number of partitions (I guess). Although, that thread has
died some time ago, so my memory can be vague.

Do you see that those patches can be used in current discussion in any way?


-- 
Best Wishes,
Ashutosh Bapat
EnterpriseDB Corporation
The Postgres Database Company



pgsql-hackers by date:

Previous
From: Amit Langote
Date:
Subject: Re: [HACKERS] New partitioning - some feedback
Next
From: Amit Langote
Date:
Subject: Re: [HACKERS] New partitioning - some feedback