Re: [HACKERS] dropping partitioned tables without CASCADE - Mailing list pgsql-hackers

From Amit Langote
Subject Re: [HACKERS] dropping partitioned tables without CASCADE
Date
Msg-id 1961d409-8979-a7e3-be1e-30f16a031c03@lab.ntt.co.jp
Whole thread Raw
In response to Re: [HACKERS] dropping partitioned tables without CASCADE  (Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>)
Responses Re: [HACKERS] dropping partitioned tables without CASCADE  (Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>)
List pgsql-hackers
On 2017/03/08 18:27, Ashutosh Bapat wrote:
>>
>> About the other statement you changed, I just realized that we should
>> perhaps do one more thing.  Show the Number of partitions, even if it's 0.
>>  In case of inheritance, the parent table stands on its own when there are
>> no child tables, but a partitioned table doesn't in the same sense.  I
>> tried to implement that in attached patch 0002.  Example below:
>>
>> create table p (a int) partition by list (a);
>> \d p
>> <snip>
>> Partition key: LIST (a)
>> Number of partitions: 0
>>
>> \d+ p
>> <snip>
>> Partition key: LIST (a)
>> Number of partitions: 0
>>
>> create table p1 partition of p for values in (1);
>> \d p
>> <snip>
>> Partition key: LIST (a)
>> Number of partitions: 1 (Use \d+ to list them.)
>>
>> \d+ p
>> <snip>
>> Partition key: LIST (a)
>> Partitions: p1 FOR VALUES IN (1)
> 
> I liked that. PFA 0002 updated. I changed one of \d output to \d+ to
> better test partitioned tables without partitions in verbose and
> non-verbose mode. Also, refactored the your code to have less number
> of conditions. Please let me know if it looks good.

Thanks, looks good.

Regards,
Amit





pgsql-hackers by date:

Previous
From: Ashutosh Sharma
Date:
Subject: Re: [HACKERS] Supporting huge pages on Windows
Next
From: Thomas Munro
Date:
Subject: Re: [HACKERS] Supporting huge pages on Windows