| From: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> |
|---|---|
| To: | Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com> |
| Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: dropping partitioned tables without CASCADE |
| Date: | 2017-02-23 06:32:02 |
| Message-ID: | 03c35118-4b0a-c288-e03f-ee738d36ee60@lab.ntt.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2017-02-23 06:36:57 | Automatic cleanup of oldest WAL segments with pg_receivexlog |
| Previous Message | Thomas Munro | 2017-02-23 06:24:34 | Re: Measuring replay lag |