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

From Ashutosh Bapat
Subject Re: [HACKERS] dropping partitioned tables without CASCADE
Date
Msg-id CAFjFpRdg8rLAjgSei3kNQX=AB-zT6U3=ML2_2AuiJBNb7VYc1A@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] dropping partitioned tables without CASCADE  (Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>)
Responses Re: [HACKERS] dropping partitioned tables without CASCADE  (Simon Riggs <simon@2ndquadrant.com>)
List pgsql-hackers
I think this is ready for committer.

On Thu, Feb 23, 2017 at 12:02 PM, Amit Langote
<Langote_Amit_f8@lab.ntt.co.jp> wrote:
> On 2017/02/22 21:24, Ashutosh Bapat wrote:
>> On Wed, Feb 22, 2017 at 11:11 AM, Amit Langote wrote:
>>> +       /*
>>> +        * Unlike inheritance children, partition tables are expected to be dropped
>>> +        * when the parent partitioned table gets dropped.
>>> +        */
>>>
>>> Hmm.  Partitions *are* inheritance children, so we perhaps don't need the
>>> part before the comma.  Also, adding "automatically" somewhere in there
>>> would be nice.
>>>
>>> Or, one could just write: /* add an auto dependency for partitions */
>>
>> I changed it in the attached patch to
>> +    /*
>> +     * Partition tables are expected to be dropped when the parent partitioned
>> +     * table gets dropped.
>> +     */
>
> OK, thanks.
>
> Thanks,
> Amit
>
>



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



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: [HACKERS] Automatic cleanup of oldest WAL segments with pg_receivexlog
Next
From: Jim Nasby
Date:
Subject: Re: [HACKERS] [PATCH] Add pg_disable_checksums() and supportinginfrastructure